From: Gunter Ohrner <G.Ohrner@post.rwth-aachen.de>
To: cpufreq@lists.linux.org.uk
Subject: Re: cpufreq: powernow-k8 frequency transitions question
Date: Tue, 03 Jan 2006 01:16:07 +0100 [thread overview]
Message-ID: <dpcfn8$16q$1@sea.gmane.org> (raw)
In-Reply-To: p73fyo6ft59.fsf@verdi.suse.de
Andi Kleen wrote:
>> I already asked this question on linux-kernel@vger.kernel.org but maybe
>> this list would be a more appropriate place...
> The proceedings of the Ottawa Linux Symposium 2004 (available online)
> have a detailed paper on the powernow-k8 driver.
Ah, thanks. I found it, read it, and will soon compare the description to
the current implementation.
From what I saw I already figured out the most important parts myself, as
the driver is rather readable, but the paper contained some interesting
additional details and reasons for some things I still wondered about.
>> How do the conservative/ondemand cpufreq governors cope with the kernel
>> advertising frequencies it cannot directly transition between?
> Step by step. The frequency/voltage transistion functions
> in powernow-k8.c go through them in loops.
Oh, ok, I must have missed that part in the driver, I will look for it.
Thanks a lot! :-)
Greetings,
Gunter
--
The students were staring at her in the manner of those who have heard
of the species 'female' but have never expected to get this close to
one. -- (Terry Pratchett, Soul Music)
*** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***
next prev parent reply other threads:[~2006-01-03 0:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-01 12:13 cpufreq: powernow-k8 frequency transitions question Gunter Ohrner
2006-01-02 17:15 ` Andi Kleen
2006-01-03 0:16 ` Gunter Ohrner [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-02 17:37 Devriendt, Paul
2006-01-03 0:19 ` Gunter Ohrner
2006-01-03 16:29 ` Bruno Ducrot
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
2006-01-04 3:12 Devriendt, Paul
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='dpcfn8$16q$1@sea.gmane.org' \
--to=g.ohrner@post.rwth-aachen.de \
--cc=cpufreq@lists.linux.org.uk \
/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