From: Scott James Remnant <scott@canonical.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Ingo Molnar <mingo@elte.hu>,
davej@codemonkey.org.uk, linux-kernel@vger.kernel.org,
cpufreq@vger.kernel.org
Subject: Re: [PATCH] cpufreq: Change link order of x86 cpufreq modules
Date: Fri, 20 Feb 2009 17:29:52 +0000 [thread overview]
Message-ID: <1235150992.6467.66.camel@quest> (raw)
In-Reply-To: <20090218183641.GA20203@srcf.ucam.org>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On Wed, 2009-02-18 at 18:36 +0000, Matthew Garrett wrote:
> On Wed, Feb 18, 2009 at 07:31:37PM +0100, Ingo Molnar wrote:
>
> > Nice fix! Where does this information come from? Distro module
> > ordering magic? It's rather non-trivial.
>
> Pretty much. p4-clockmod is never the preferred option because it does
> no voltage scaling. speedstep-centrino is now almost entirely
> functionally replaced with acpi-cpufreq. The powernow-k8 issue was a
> personal communication from davej.
>
In fact, we've noticed severe regressions with p4-clockmod over simply
having no scaling driver at all - and are not going to built it into our
kernels.
Scott
--
Scott James Remnant
scott@canonical.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-20 17:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 18:28 [PATCH] cpufreq: Change link order of x86 cpufreq modules Matthew Garrett
2009-02-18 18:31 ` Ingo Molnar
2009-02-18 18:34 ` Dave Jones
2009-02-18 18:36 ` Matthew Garrett
2009-02-18 19:09 ` Ingo Molnar
2009-02-19 11:54 ` Alan Jenkins
2009-02-19 12:03 ` Ingo Molnar
2009-02-23 21:12 ` Thomas Renninger
2009-02-23 21:47 ` Kay Sievers
2009-02-20 17:29 ` Scott James Remnant [this message]
2009-02-20 17:36 ` Matthew Garrett
2009-02-20 17:39 ` Scott James Remnant
2009-02-20 17:41 ` Dave Jones
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=1235150992.6467.66.camel@quest \
--to=scott@canonical.com \
--cc=cpufreq@vger.kernel.org \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.org \
/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.