All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: "Anthony L. Awtrey" <tony@awtrey.com>
Cc: Dave Jones <davej@codemonkey.org.uk>, Greg KH <gregkh@suse.de>,
	Stable <Stable@kernel.org>,
	cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] Make acpi-cpufreq more robust against BIOS freq changes behind our back
Date: Wed, 21 May 2008 15:15:01 +0200	[thread overview]
Message-ID: <1211375701.29901.11.camel@queen.suse.de> (raw)
In-Reply-To: <1211375286.29901.7.camel@queen.suse.de>

On Wed, 2008-05-21 at 15:08 +0200, Thomas Renninger wrote:
> Hi,
> 
> Please consider this one for stable integration.
...
> If this one patches for you for 2.6.24.4 also, maybe it even gets in
> there.
Hmm, I added this to OpenSUSE 10.3, means 2.6.22.
I only had to adjust the arch/i386 vs arch/x86 patch.
If this gets into the stable kernel, I wonder how far back this makes
sense. Shall I send a 2.6.22 based version?

   Thomas
> 
> ------------
> 
> commit e56a727b023d40d1adf660168883f30f2e6abe0a
> Author: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> Date:   Mon Apr 28 15:13:43 2008 -0400
> 
>     [CPUFREQ] Make acpi-cpufreq more robust against BIOS freq changes behind our back.
>     
>     We checked the hardware freq with OS cached freq value in get_cur_freqon_cpu().
>     
>     Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
>     Signed-off-by: Thomas Renninger <trenn@suse.de>
>     Signed-off-by: Dave Jones <davej@redhat.com>
> 
> diff --git a/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c b/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c
> index e2d870d..8db8f73 100644
> --- a/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c
> +++ b/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c
> @@ -339,6 +339,7 @@ static unsigned int get_cur_freq_on_cpu(unsigned int cpu)
>  {
>  	struct acpi_cpufreq_data *data = per_cpu(drv_data, cpu);
>  	unsigned int freq;
> +	unsigned int cached_freq;
>  
>  	dprintk("get_cur_freq_on_cpu (%d)\n", cpu);
>  
> @@ -347,7 +348,16 @@ static unsigned int get_cur_freq_on_cpu(unsigned int cpu)
>  		return 0;
>  	}
>  
> +	cached_freq = data->freq_table[data->acpi_data->state].frequency;
>  	freq = extract_freq(get_cur_val(&cpumask_of_cpu(cpu)), data);
> +	if (freq != cached_freq) {
> +		/*
> +		 * The dreaded BIOS frequency change behind our back.
> +		 * Force set the frequency on next target call.
> +		 */
> +		data->resume = 1;
> +	}
> +
>  	dprintk("cur freq = %u\n", freq);
>  
>  	return freq;
> 
> 
> 
> _______________________________________________
> Cpufreq mailing list
> Cpufreq@lists.linux.org.uk
> http://lists.linux.org.uk/mailman/listinfo/cpufreq

  reply	other threads:[~2008-05-21 13:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 18:15 acpi_cpufreq stepping issue on Pentium M 1.2GHz Anthony L. Awtrey
2008-05-19  0:08 ` Dave Jones
2008-05-19 11:29   ` Anthony L. Awtrey
2008-05-19 13:14     ` Dave Jones
2008-05-19 13:38       ` Anthony L. Awtrey
2008-05-20 10:38   ` Thomas Renninger
2008-05-21 12:51     ` Anthony L. Awtrey
2008-05-21 13:08       ` [PATCH] Make acpi-cpufreq more robust against BIOS freq changes behind our back Thomas Renninger
2008-05-21 13:15         ` Thomas Renninger [this message]
2008-05-21 15:00           ` [stable] " Greg KH
2008-05-21 18:48           ` Anthony L. Awtrey
2008-05-23  9:20             ` Thomas Renninger
2008-05-21 15:46         ` Anthony L. Awtrey
2008-06-02 22:36           ` [stable] " Chris Wright
2008-06-11 14:33             ` Thomas Renninger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1211375701.29901.11.camel@queen.suse.de \
    --to=trenn@suse.de \
    --cc=Stable@kernel.org \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=davej@codemonkey.org.uk \
    --cc=gregkh@suse.de \
    --cc=tony@awtrey.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.