From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: announce: PPSkit patch for Linux 2.4.2 (pre6)
Date: 11 Apr 2001 10:56:01 -0700 [thread overview]
Message-ID: <9b25rh$rav$1@cesium.transmeta.com> (raw)
In-Reply-To: <3AC83FF1.27420.398B86@localhost> <3AD2CE98.28151.46E93A@localhost>
Followup to: <3AD2CE98.28151.46E93A@localhost>
By author: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
In newsgroup: linux.dev.kernel
>
> Hi, Cycle Counters,
>
> Linux currently tries to synchronize TSCs for consistent time in SMP
> systems. One would not believe what combinations of hardware are tried,
> especially for precision timing. Here's a short answer to my asking-
> back about a complaint (the kernel is reporting negative time warps).
>
> As any problem, it can be solved with some overhead, but should it be
> done?
>
> Replies to me too, as I'm not subscribed, please.
>
> >
> > I have to tell you that I have one 533 MHz Celeron and one 433 MHz
> > Celeron.
> >
Hi there,
We have talked about assymmetric multiprocessor configurations once or
twice around. The easy way to deal with them is simply to use
"no-tsc" on the command line (and/or compile your kernel
appropriately.) One could, at least theoretically, make them usable
in kernel space only (in user space there is no hope, since you can't
know which CPU's TSC you're reading), but these machines seem to be so
rare that hardly anyone technical enough to fix it cares.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
next prev parent reply other threads:[~2001-04-11 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0104091815160.1367-300000@terran.bussi.de>
[not found] ` <3AC83FF1.27420.398B86@localhost>
2001-04-10 7:12 ` announce: PPSkit patch for Linux 2.4.2 (pre6) Ulrich Windl
2001-04-11 17:56 ` H. Peter Anvin [this message]
2001-04-11 18:03 ` Alan Cox
2001-04-11 18:18 ` H. Peter Anvin
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='9b25rh$rav$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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