cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gunter Ohrner <G.Ohrner@post.rwth-aachen.de>
To: cpufreq@lists.linux.org.uk
Subject: Re: cpufreq: powernow-k8 frequency transitions question
Date: Sat, 07 Jan 2006 15:28:12 +0100	[thread overview]
Message-ID: <dpoj4u$87s$1@sea.gmane.org> (raw)
In-Reply-To: 43BB29FF.2000401@gmail.com

Nebojsa Trpkovic wrote:
> The most usefull powersaving is achieved by lowering the voltage and not 
> the further lowering of frequency.

Yes, but lower clock speeds usually allow for lower voltages, so that's what
you gain by lowering the core frequency.

> minimum stable voltage just to be 110% sure it will work stable:
> Winchester runs with 1.0GHz @1.0V and 1.8GHz @1.275V

I'm currently running my Winchester 3000+ at 1,0GHZ@1,0V and 1,8GHz@1,15V
only, and it's rock solid for me so far - it survived hours of 100% cpu
load during normal operation and using cpuburn's burnK7, either locked at
on of the frequencies or in dynamic mode using the ondemand governor.

> So, I've modified powernow-k8.c to lower the voltages read from BIOS for 
> every p-state.

Changing the vlaues returned by the BIOS by a function is a really
interesting approach, especially if there's not much point in providing
additional P-states, which is my current impression. At the moment I have
ACPI table queries turned off in powernow-k8 and supply a hand craftes PSB
table, but obviously that's not the most flexible solution. Mh, two VID and
FID mapping function's which initially are identity functions but with some
sysfs-tuneable parameters sounds interesting to me... :-)

I guess I should try that.

Greetings and thanks for that idea,

  Gunter

-- 
The question seldom addressed is *where* Medusa had snakes. Underarm 
hair is an even more embarassing problem when it keeps biting the top 
of the deodorant bottle.        -- (Terry Pratchett, Soul Music)
*** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***

  parent reply	other threads:[~2006-01-07 14:28 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
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 [this message]
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='dpoj4u$87s$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