From: "H. Peter Anvin" <hpa@zytor.com>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Missed jiffies
Date: Tue, 19 Feb 2002 12:23:46 -0800 [thread overview]
Message-ID: <3C72B452.20102@zytor.com> (raw)
In-Reply-To: <3C6E77DE.70FE49DF@rwii.com> <3C6E833F.1A888B3C@mvista.com> <a4pbvi@cesium.transmeta.com> <20020219093052.B37@toy.ucw.cz>
Pavel Machek wrote:
> Hi!
>
>
>>>lap tops), is the fact that TSC is NOT clocked at a fixed rate. It is
>>>affected by throttling (reduced in 12.5% increments) and by power
>>>management.
>>>
>>If the TSC is affected by HLT, throttling, or C2 power management, the
>>TSC is broken (as it is on Cyrix chips, for example.) The TSC usually
>>*is* affected by C3 power management, but the OS should be aware of
>>C3.
>>
>
> Add thinkpad 560X (pentium/MMX) and toshiba 4030cdt (celeron) to your
> blacklist, then. I believe that by your definition *many* sstems are
> broken.
> Pavel
It's sad but true. Unfortunately the TSC seems to be considered a
low-priority operation. It's for systems like the above you need the
"no-tsc" option.
-hpa
next prev parent reply other threads:[~2002-02-19 20:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-16 15:16 Missed jiffies Tyson D Sawyer
2002-02-16 16:05 ` george anzinger
2002-02-16 16:14 ` yodaiken
2002-02-16 17:11 ` Alan Cox
2002-02-17 2:18 ` disregard lee johnson
2002-02-17 22:48 ` Missed jiffies H. Peter Anvin
2002-02-18 19:04 ` george anzinger
2002-02-18 19:22 ` H. Peter Anvin
2002-02-18 19:33 ` Alan Cox
[not found] ` <a4pbvi@cesium.transmeta.com>
2002-02-19 9:30 ` Pavel Machek
2002-02-19 20:23 ` H. Peter Anvin [this message]
2002-02-16 16:46 ` Alan Cox
2002-02-16 18:44 ` Eric W. Biederman
2002-02-16 19:02 ` george anzinger
2002-02-19 9:25 ` Pavel Machek
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=3C72B452.20102@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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.