mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>,
	torvalds@transmeta.com, padraig@antefacto.com,
	linux-kernel@vger.kernel.org
Subject: Re: CPU frequency shifting "problems"
Date: Mon, 1 Oct 2001 09:28:50 +0000	[thread overview]
Message-ID: <20011001092850.A35@toy.ucw.cz> (raw)
In-Reply-To: <8FB7D6BCE8A2D511B88C00508B68C2081971D8@orsmsx102.jf.intel.com>
In-Reply-To: <8FB7D6BCE8A2D511B88C00508B68C2081971D8@orsmsx102.jf.intel.com>; from andrew.grover@intel.com on Thu, Sep 27, 2001 at 06:24:56PM -0700

Hi!

> > > For example, the Intel "SpeedStep" CPU's are completely broken under
> > > Linux, and real-time will advance at different speeds in DC 
> > and AC modes,
> > > because Intel actually changes the frequency of the TSC 
> > _and_ they don't
> > > document how to figure out that it changed.
> > 
> > The change is APM or ACPI initiated. Intel won't tell anyone anything
> > useful but Microsoft have published some of the required 
> > intel confidential
> > information which helps a bit
> 
> APM is a lost cause, but the correct solution for ACPI systems is to use the
> PM timer. This totally obviates the need to really care about the CPU's
> effective frequency at all. Even if you knew all the details of SpeedStep
> (and I've seen the same MS doc you have Alan and was surprised at its
> detail) you'd still be hosed if the CPU throttles...you'd be hosed in a
> *good* way because at least any delays would be longer (not shorter) than
> expected but your times would be off nonetheless.

And if it is thermal-throttledduring bogomips calibration...? [Well possible,
acpi is not active that early]

-- 
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.


  parent reply	other threads:[~2001-10-02 21:34 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
2001-09-28 22:30 ` Alan Cox
2001-10-01  9:28 ` Pavel Machek [this message]
     [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=20011001092850.A35@toy.ucw.cz \
    --to=pavel@suse.cz \
    --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®