From: Chris Wright <chrisw@sous-sol.org>
To: "Anthony L. Awtrey" <tony@awtrey.com>
Cc: Dave Jones <davej@codemonkey.org.uk>,
cpufreq@lists.linux.org.uk, Greg KH <gregkh@suse.de>,
Stable <Stable@kernel.org>
Subject: Re: [stable] [PATCH] Make acpi-cpufreq more robust against BIOS freq changes behind our back
Date: Mon, 2 Jun 2008 15:36:17 -0700 [thread overview]
Message-ID: <20080602223617.GO30402@sequoia.sous-sol.org> (raw)
In-Reply-To: <483443BE.9000002@awtrey.com>
* Anthony L. Awtrey (tony@awtrey.com) wrote:
> On 05/21/2008 09:08 AM, Thomas Renninger wrote:
> > 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);
-^-
This does not apply cleanly to 2.6.25.4 (doesn't have commit: fc0e4748).
> I worked! This patch applied to 2.6.25.4 fixed the CPU stepping problem
> on the Panasonic CF-18 (Pentium M) I was having.
I suppose you manually applied the patch?
Anyway, I backported and will add to -stable, please holler if this is
wrong.
thanks,
-chris
next prev parent reply other threads:[~2008-06-02 22:36 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
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 ` Chris Wright [this message]
2008-06-11 14:33 ` [stable] " 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=20080602223617.GO30402@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--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.