mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@tux.tmfweb.nl, 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: Thu, 28 Oct 2004 02:17:54 +0200	[thread overview]
Message-ID: <20041028001754.GG23595@wotan.suse.de> (raw)
In-Reply-To: <1098913837.7783.8.camel@localhost.localdomain>

On Wed, Oct 27, 2004 at 10:50:38PM +0100, Alan Cox wrote:
> 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.

It depends on the BIOS. hlt can do it with the right SMM code.
Other than that you need ACPI.

The main reason that BIOS don't use the more advanced power saving
modi is that they tend to have much longer latencies, and hlt cannot
know what interrupt latency the OS wants. A lot of BIOS seem 
to go for short latency for compatibility.

That is why using the ACPI processor driver is a much better
choice, because it actually tries to figure this out and use the
correct sleep mode for the load.  It doesn't do it very well on Linux yet
though because of lacking infrastructure in the main kernel
(e.g. it needs better accounting for interrupts) , but I hope 
that can be eventually improved.

<insert standard rant about the the 1ms timer tick that also
doesn't help at all for this>

-Andi

  reply	other threads:[~2004-10-28  0:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-27 14:43 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
2004-10-28  0:17       ` Andi Kleen [this message]
  -- 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=20041028001754.GG23595@wotan.suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®