Re: [PATCH v2 1/2] nohz: add tick_nohz_full_clear_cpus() and _set_cpus() APIs

* Chris Metcalf wrote: > On 04/06/2015 02:29 PM, Frederic Weisbecker wrote: > >On Mon, Apr 06, 2015 at 02:16:44PM -0400,cmetc...@ezchip.com wrote: > >>>From: Chris Metcalf > >>> > >>>The "clear" API is useful, for example, to modify a cpumask to avoid > >>>the nohz cores so that interrupts aren

Re: [PATCH v2 1/2] nohz: add tick_nohz_full_clear_cpus() and _set_cpus() APIs

On 04/06/2015 02:29 PM, Frederic Weisbecker wrote: On Mon, Apr 06, 2015 at 02:16:44PM -0400,cmetc...@ezchip.com wrote: >From: Chris Metcalf > >The "clear" API is useful, for example, to modify a cpumask to avoid >the nohz cores so that interrupts aren't sent to them. > >Likewise the "set" API i

Re: [PATCH v2 1/2] nohz: add tick_nohz_full_clear_cpus() and _set_cpus() APIs

On Mon, Apr 06, 2015 at 02:16:44PM -0400, cmetc...@ezchip.com wrote: > From: Chris Metcalf > > The "clear" API is useful, for example, to modify a cpumask to avoid > the nohz cores so that interrupts aren't sent to them. > > Likewise the "set" API is useful to modify a cpumask indicating some >

[PATCH v2 1/2] nohz: add tick_nohz_full_clear_cpus() and _set_cpus() APIs

From: Chris Metcalf The "clear" API is useful, for example, to modify a cpumask to avoid the nohz cores so that interrupts aren't sent to them. Likewise the "set" API is useful to modify a cpumask indicating some special nohz-type functionality so that the nohz cores are automatically added to t