From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: linux-kernel@tux.tmfweb.nl
Cc: Paulo Marques <pmarques@grupopie.com>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Andi Kleen <ak@suse.de>,
akpm@osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add p4-clockmod driver in x86-64
Date: Wed, 27 Oct 2004 22:50:38 +0100 [thread overview]
Message-ID: <1098913837.7783.8.camel@localhost.localdomain> (raw)
In-Reply-To: <20041027213807.GA9334@nospam.com>
On Mer, 2004-10-27 at 22:38, Rutger Nijlunsing wrote:
> So you've got the _disadvantages_ of a slow clock (programs run
> slower), and not the _advantages_ (power consumption is same as idle
> CPU and not lower, temperature is same as idle CPU and not lower).
>
> But why does the P4 have such a mode? It uses this mode during thermal
> throttling to get to the 'idle' temperature.
It isn't obvious how you software idle a PIV - "hlt" at least does not
seem to do that.
> Therefore, p4-clockmod is completely misnamed: it's _not_ a cpufreq
> driver in the sense that it does not change the frequency.
It performs a similar function less efficiently. Lots of older chipsets
for K6 and the like also only support this form of clock control.
Alan
next prev parent reply other threads:[~2004-10-27 23:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 14:43 [PATCH] Add p4-clockmod driver in x86-64 Pallipadi, Venkatesh
2004-10-27 14:59 ` Paulo Marques
2004-10-27 15:56 ` Lee Revell
2004-10-27 16:14 ` Paulo Marques
2004-10-27 16:22 ` Alan Cox
2004-10-27 18:47 ` Marcus Metzler
2004-10-27 21:38 ` Rutger Nijlunsing
2004-10-27 21:50 ` Alan Cox [this message]
2004-10-28 0:17 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2004-10-27 16:39 Pallipadi, Venkatesh
2004-10-26 21:28 Venkatesh Pallipadi
2004-10-27 3:18 ` Andi Kleen
2004-10-28 0:10 ` Andi Kleen
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=1098913837.7783.8.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@tux.tmfweb.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=pmarques@grupopie.com \
--cc=venkatesh.pallipadi@intel.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 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.