linux-kernel - Re: [PATCH 1/2] acpi-cpufreq: Fix CPU_ANY CPUFREQ

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:	Tue, 27 Apr 2010 10:08:17 -0700
From:	Venkatesh Pallipadi <venki@...gle.com>
To:	Thomas Renninger <trenn@...e.de>
Cc:	x86@...nel.org, linux-trace-users@...r.kernel.org,
	linux-perf-users@...r.kernel.org, robert.schoene@...dresden.de,
	cpufreq@...r.kernel.org, linux-kernel@...r.kernel.org,
	davej@...hat.com, arjan@...radead.org
Subject: Re: [PATCH 1/2] acpi-cpufreq: Fix CPU_ANY CPUFREQ_{PRE,POST}CHANGE 
	notification

Acked-by: Venkatesh Pallipadi <venki@...gle.com>

On Tue, Apr 27, 2010 at 7:57 AM, Thomas Renninger <trenn@...e.de> wrote:
>
> This has been found be review.
> Currently PRE/POSTCHANGE events seem to only be thrown for one core
> if the BIOS tells us to run in CPU_ANY mode (switching one/any
> of the depending cores is enough).
>
> Signed-off-by: Thomas Renninger <trenn@...e.de>
> CC: venki@...gle.com
> CC: davej@...hat.com
> CC: linux-kernel@...r.kernel.org
> CC: cpufreq@...r.kernel.org
> CC: linux-perf-users@...r.kernel.org
> CC: linux-trace-users@...r.kernel.org
> CC: x86@...nel.org
> CC: robert.schoene@...dresden.de
> ---
>  arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c b/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c
> index 4591680..c6de3a9 100644
> --- a/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c
> +++ b/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c
> @@ -391,7 +391,7 @@ static int acpi_cpufreq_target(struct cpufreq_policy *policy,
>
>        freqs.old = perf->states[perf->state].core_frequency * 1000;
>        freqs.new = data->freq_table[next_state].frequency;
> -       for_each_cpu(i, cmd.mask) {
> +       for_each_cpu(i, policy->cpus) {
>                freqs.cpu = i;
>                cpufreq_notify_transition(&freqs, CPUFREQ_PRECHANGE);
>        }
> @@ -407,7 +407,7 @@ static int acpi_cpufreq_target(struct cpufreq_policy *policy,
>                }
>        }
>
> -       for_each_cpu(i, cmd.mask) {
> +       for_each_cpu(i, policy->cpus) {
>                freqs.cpu = i;
>                cpufreq_notify_transition(&freqs, CPUFREQ_POSTCHANGE);
>        }
> --
> 1.6.3
>
--
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/