cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Gunter Ohrner <G.Ohrner@post.rwth-aachen.de>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: cpufreq: powernow-k8 frequency transitions question
Date: 02 Jan 2006 18:15:30 +0100	[thread overview]
Message-ID: <p73fyo6ft59.fsf@verdi.suse.de> (raw)
In-Reply-To: <dp8h08$du6$1@sea.gmane.org>

Gunter Ohrner <G.Ohrner@post.rwth-aachen.de> writes:

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

> I'm currently reading and playing with the powernow-k8 cpufreq driver
> module. However so far I wasn't able to find out how frequency transitions
> are dealt with that have to be made using intermediate steps, ie.
> transitions which cannot be done in one single step.
> 
> (I read about this at 
> http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/26094.PDF
> p. 269f.)
> 
> I found safety guards which return an error if an invalid frequency
> transition ("lo-lo transition") is requested. Is this the only support for
> these transitions currently implemented or did I miss something?
> Is there more advanced support simply missing, or is the current behaviour
> sufficient, and if yes, why does this suffice?
> 
> 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.

-Andi

  reply	other threads:[~2006-01-02 17:15 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 [this message]
2006-01-03  0:16   ` Gunter Ohrner
  -- 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=p73fyo6ft59.fsf@verdi.suse.de \
    --to=ak@suse.de \
    --cc=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