From: Bruno Ducrot <ducrot@poupinou.org>
To: "Devriendt, Paul" <paul.devriendt@amd.com>
Cc: Gunter Ohrner <G.Ohrner@post.rwth-aachen.de>, cpufreq@lists.linux.org.uk
Subject: Re: cpufreq: powernow-k8 frequency transitions question
Date: Tue, 3 Jan 2006 17:29:46 +0100 [thread overview]
Message-ID: <20060103162946.GF13887@poupinou.org> (raw)
In-Reply-To: <84EA05E2CA77634C82730353CBE3A84303D430BD@SAUSEXMB1.amd.com>
On Mon, Jan 02, 2006 at 11:37:12AM -0600, Devriendt, Paul wrote:
> > I found safety guards which return an error if an invalid frequency
> > transition ("lo-lo transition") is requested.
>
> Transitions between low frequencies (<=1.4GHz) are not supported by
> hardware. The way to do them is to transition to an intermediate
> high frequency. No BIOSs define two low PStates so the case never
> occurs, but it could theoretically be done. The AMD BIOS and Kernel
> Developers Guide available on AMD's web site provides more information
> on K8 PStates.
I'm wondering if this would have some more power saving if there are more
low p-states. I should some day look at this more seriously.
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2006-01-03 16:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 17:37 cpufreq: powernow-k8 frequency transitions question Devriendt, Paul
2006-01-03 0:19 ` Gunter Ohrner
2006-01-03 16:29 ` Bruno Ducrot [this message]
2006-01-04 0:47 ` Gunter Ohrner
2006-01-04 1:50 ` Nebojsa Trpkovic
2006-01-04 10:45 ` Bruno Ducrot
2006-01-04 13:04 ` Nebojsa Trpkovic
2006-01-07 14:31 ` Gunter Ohrner
2006-01-07 14:28 ` Gunter Ohrner
2006-01-08 2:32 ` Gunter Ohrner
-- strict thread matches above, loose matches on Subject: below --
2006-01-04 3:12 Devriendt, Paul
2006-01-01 12:13 Gunter Ohrner
2006-01-02 17:15 ` Andi Kleen
2006-01-03 0:16 ` Gunter Ohrner
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=20060103162946.GF13887@poupinou.org \
--to=ducrot@poupinou.org \
--cc=G.Ohrner@post.rwth-aachen.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=paul.devriendt@amd.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