linux-kernel - Re: [PATCH] cpuidle: move field disable from per-driver to per-cpu

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, 14 Jun 2012 10:41:27 -0400
From:	"Andrew J. Schorr" <aschorr@...emetry-investments.com>
To:	ShuoX Liu <shuox.liu@...el.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Brown, Len" <len.brown@...el.com>,
	"Zhang, Yanmin" <yanmin.zhang@...el.com>,
	Deepthi Dharwar <deepthi@...ux.vnet.ibm.com>
Subject: Re: [PATCH] cpuidle: move field disable from per-driver to per-cpu

Hi,

On Thu, Jun 14, 2012 at 10:52:48AM +0800, ShuoX Liu wrote:
> Andrew J.Schorr raises a question. When he changes the disable setting
> on a single CPU, it affects all the other CPUs. Basically, currently,
> the disable field is per-driver instead of per-cpu. All the C states of
> the same driver are shared by all CPU in the same machine.
> 
> Below patch changes field disable to per-cpu, so we could set this
> separately for each cpu.

Thanks.  I have not tested this, but it looks very useful to have the
flexibility to disable certain C states on a subset of the cores.  The current
implementation affecting all cores is much less powerful.

Thanks,
Andrew
--
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/