linux-kernel - Re: [PATCH v2 0/2] new cpumask for hotpluggable CPUs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 11 Aug 2011 12:25:53 -0700
From:	"Turquette, Mike" <mturquette@...com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org,
	linaro-dev@...ts.linaro.org, patches@...aro.org, gregkh@...e.de
Subject: Re: [PATCH v2 0/2] new cpumask for hotpluggable CPUs

On Thu, Aug 11, 2011 at 11:30 AM, Peter Zijlstra <peterz@...radead.org> wrote:
> On Wed, 2011-08-10 at 13:03 -0700, Mike Turquette wrote:
>> This patch series introduces a new cpumask which tracks CPUs that
>> support hotplugging.  The purpose of this patch series is to provide a
>> simple method for kernel code to know which CPUs can be hotplugged and
>> which ones cannot.  Potential users of this code might be a thermal
>> mitigation technique which uses hotplug to lower temperature, or a power
>> capping mechanism which uses hotplug to lower power consumption.
>>
>> All the of usual cpumask helper functions are created for this new mask.
>> The second patch in this series simply sets the bit for elligible CPUs
>> while they are being registered.  The cpumask itself is static after
>> boot and should not change (like the possbile mask).
>
> I still most strongly object to people using hotplug for these goals.
>
> Why do you need to go through the entire dance of hotplug just to idle a
> cpu? Hotplug not only idles the cpu but tears down (and rebuilds) an
> insane amount of resources associated with the cpu.

I think you're nacking the wrong series.  This patchset simply allows
kernel space to know which CPUs can go offline and which one can't,
which seems pretty innocuous.  Are you fundamentally opposed to the
kernel having better accessor functions to this data?

I'll soon be posting some code which does implement hotplug as a
power-capping feature.  I think *that* is the patch that you'll want
to nack.

Thanks for reviewing,
Mike

> Nacked-by: Peter Zijlstra <a.p.zijlstra@...llo.nl>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/