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]

Message-Id: <20120622161030.da016ccf.akpm@linux-foundation.org>
Date:	Fri, 22 Jun 2012 16:10:30 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	shuox.liu@...el.com
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Brown, Len" <len.brown@...el.com>,
	"Zhang, Yanmin" <yanmin.zhang@...el.com>,
	"Andrew J. Schorr" <aschorr@...emetry-investments.com>,
	Deepthi Dharwar <deepthi@...ux.vnet.ibm.com>
Subject: Re: [PATCH] cpuidle: move field disable from per-driver to per-cpu

On Thu, 14 Jun 2012 10:52:48 +0800
ShuoX Liu <shuox.liu@...el.com> wrote:

> From: ShuoX Liu <shuox.liu@...el.com>
> 
> 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.
> 
> ...
>
> --- a/include/linux/cpuidle.h
> +++ b/include/linux/cpuidle.h
> @@ -34,6 +34,7 @@ struct cpuidle_driver;
>  struct cpuidle_state_usage {
>  	void		*driver_data;
>  
> +	unsigned long long	disable;

hrmpf.  We're using 64 bits for this where one bit would do, afaict
because the magic macros in drivers/cpuidle/sysfs.c are using %llu.

--
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/