linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Scott James Remnant <scott@canonical.com>
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:36:37 +0000	[thread overview]
Message-ID: <20090220173637.GA1985@srcf.ucam.org> (raw)
In-Reply-To: <1235150992.6467.66.camel@quest>

On Fri, Feb 20, 2009 at 05:29:52PM +0000, Scott James Remnant wrote:

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

It makes sense to have p4-clockmod from a thermal management 
perspective. We should probably bump its transition latency to more than 
10ms to prevent ondemand binding to it.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2009-02-20 17:37 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
2009-02-20 17:36       ` Matthew Garrett [this message]
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=20090220173637.GA1985@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=scott@canonical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).