All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: CPU throttling??
Date: 3 Feb 2003 14:14:23 -0800	[thread overview]
Message-ID: <b1mpjv$mfq$1@cesium.transmeta.com> (raw)
In-Reply-To: 20030203211806.GA21312@codemonkey.org.uk

Followup to:  <20030203211806.GA21312@codemonkey.org.uk>
By author:    Dave Jones <davej@codemonkey.org.uk>
In newsgroup: linux.dev.kernel
> 
> Most (all?[1]) other modern x86 mobile processors behave the way I mentioned.
> AMD Powernow (K6 and K7), VIA longhaul/powersaver all have optimal voltages
> they can be run at when clocked to different speeds. By way of example, a table from
> my mobile athlon..
> 
>     FID: 0x12 (4.0x [532MHz])   VID: 0x13 (1.200V)
>     FID: 0x4 (5.0x [665MHz])    VID: 0x13 (1.200V)
>     FID: 0x6 (6.0x [798MHz])    VID: 0x13 (1.200V)
>     FID: 0xa (8.0x [1064MHz])   VID: 0xd (1.350V)
>     FID: 0xf (10.5x [1396MHz])  VID: 0x9 (1.550V)
> 
> Sure I *could* run that at 523MHz and still pump 1.550V into it,
> but why would I want to do that ?
> 
> 		Dave
> 
> [1] Unsure about the crusoe.
> 

Crusoe changes frequency and voltages on the fly, transparently to the
operating system.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: cris ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64

  parent reply	other threads:[~2003-02-03 22:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03 21:14 CPU throttling?? Grover, Andrew
2003-02-03 21:18 ` Dave Jones
2003-02-03 21:41   ` John Bradford
2003-02-03 22:14   ` H. Peter Anvin [this message]
2003-02-03 22:31 ` Ville Herva
2003-02-04 10:22 ` Seamus
2003-02-04 10:31   ` John Bradford
2003-02-04 11:01     ` Seamus
  -- strict thread matches above, loose matches on Subject: below --
2003-02-03 21:51 Grover, Andrew
2003-02-03 15:47 Joeri Belis
2003-02-03 16:55 ` CPU throttling?? Seamus
2003-02-03 17:00   ` Dave Jones
2003-02-03 17:04   ` Martin Hermanowski
2003-02-03 17:13   ` John Bradford
2003-02-03 18:57     ` Valdis.Kletnieks
2003-02-03 19:02       ` Dave Jones
2003-02-03 19:09       ` Martin Hermanowski
2003-02-03 19:20         ` John Bradford
2003-02-04 14:12           ` Erik Mouw
2003-02-03 19:14       ` Matt Reppert
2003-02-03 19:24         ` Valdis.Kletnieks
2003-02-04 14:34           ` Daniel Egger

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='b1mpjv$mfq$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.