mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Morton <chromi@cyberspace.org>
To: Linus Torvalds <torvalds@transmeta.com>,
	"Grover, Andrew" <andrew.grover@intel.com>
Cc: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>, <padraig@antefacto.com>,
	<linux-kernel@vger.kernel.org>
Subject: RE: CPU frequency shifting "problems"
Date: Sat, 29 Sep 2001 01:37:46 +0100	[thread overview]
Message-ID: <a05100304b7dac7cac7e3@[192.168.239.101]> (raw)
In-Reply-To: <Pine.LNX.4.33.0109281452330.4008-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0109281452330.4008-100000@penguin.transmeta.com>

>  > APM is a lost cause, but the correct solution for ACPI systems is 
>to use the
>>  PM timer.
>
>This is _completely_ untrue.
>
>The PM timer is (a) inaccurate and (b) slow as hell.
>
>Linux uses TSC because we want high accuracy (nanosecond scale) without
>having slow stuff.

Please, don't confuse accuracy with precision.  The TSC is precise 
but not accurate.  The 100Hz timer is more accurate, especially given 
a SpeedStep CPU, but much less precise.  It's a subtle distinction, 
but an important one.

-- 
--------------------------------------------------------------
from:     Jonathan "Chromatix" Morton
mail:     chromi@cyberspace.org  (not for attachments)
website:  http://www.chromatix.uklinux.net/vnc/
geekcode: GCS$/E dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$
           V? PS PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
tagline:  The key to knowledge is not to rely on people to teach you it.

  reply	other threads:[~2001-09-29  0:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-28  1:24 Grover, Andrew
2001-09-28 21:54 ` Linus Torvalds
2001-09-29  0:37   ` Jonathan Morton [this message]
2001-09-28 22:30 ` Alan Cox
2001-10-01  9:28 ` Pavel Machek
     [not found] <8FB7D6BCE8A2D511B88C00508B68C2081971E4@orsmsx102.jf.intel.com>
2001-09-28 23:09 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2001-09-28 22:47 Grover, Andrew
2001-09-29  1:10 ` Gerhard Mack
2001-09-26 18:24 Locking comment on shrink_caches() Linus Torvalds
2001-09-26 18:40 ` Dave Jones
2001-09-26 19:12   ` Linus Torvalds
2001-09-27 12:22     ` CPU frequency shifting "problems" Padraig Brady
2001-09-27 12:44       ` Dave Jones
2001-09-27 23:23       ` Linus Torvalds
2001-09-28  0:55         ` Alan Cox
2001-09-28  2:12           ` Stefan Smietanowski
2001-09-28  8:55         ` Jamie Lokier
2001-09-28 16:11           ` Linus Torvalds
2001-09-28 20:29             ` Eric W. Biederman
2001-09-28 22:24               ` Jamie Lokier

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='a05100304b7dac7cac7e3@[192.168.239.101]' \
    --to=chromi@cyberspace.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrew.grover@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=padraig@antefacto.com \
    --cc=torvalds@transmeta.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®