From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: johnstul@us.ibm.com, jamesclv@us.ibm.com, ak@suse.de,
alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
anton.wilson@camotion.com
Subject: Re: do_gettimeofday vs. rdtsc in the scheduler
Date: Wed, 18 Sep 2002 01:52:09 +0200 [thread overview]
Message-ID: <20020918015209.B31263@wotan.suse.de> (raw)
In-Reply-To: <20020917.163246.113965700.davem@redhat.com>
On Tue, Sep 17, 2002 at 04:32:46PM -0700, David S. Miller wrote:
> From: john stultz <johnstul@us.ibm.com>
> Date: 17 Sep 2002 16:32:15 -0700
>
> Additionally, where is this system tick thing? You make it sound like
> its a register in the cpu, and while the Ultra-III may have one, I'm
> unaware of a system/bus tick register on intel chips. Is it in some
> semi-documented MSR?
>
> It's in a register on Ultra-III. The whole point of this
> conversation, if you read my initial postings, is that
> "this should have been specified in the x86 architecture"
>
> I know full well it isn't currently :-)
Sorry, it's wrong. The x86 architecture has several such registers
(apic timers, 8253 timer, HPET [Microsoft requires this for new
hardware that will be w*s certified])
They just all suck on various systems or in general. HPET is ok,
but still not widespread enough.
-Andi
next prev parent reply other threads:[~2002-09-17 23:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200209172020.g8HKKPF13227@eng2.beaverton.ibm.com.suse.lists.linux.kernel>
[not found] ` <1032294559.22815.180.camel@cog.suse.lists.linux.kernel>
[not found] ` <20020917.133933.69057655.davem@redhat.com.suse.lists.linux.kernel>
2002-09-17 21:00 ` do_gettimeofday vs. rdtsc in the scheduler Andi Kleen
2002-09-17 20:54 ` David S. Miller
2002-09-17 21:28 ` Alan Cox
2002-09-17 21:18 ` David S. Miller
2002-09-17 22:02 ` James Cleverdon
2002-09-17 22:44 ` Andi Kleen
2002-09-17 22:38 ` David S. Miller
2002-09-17 22:55 ` James Cleverdon
2002-09-17 23:12 ` David S. Miller
2002-09-17 23:32 ` john stultz
2002-09-17 23:32 ` David S. Miller
2002-09-17 23:52 ` Andi Kleen [this message]
2002-09-17 23:46 ` David S. Miller
2002-09-17 23:58 ` Andi Kleen
2002-09-17 23:51 ` David S. Miller
2002-09-18 0:05 ` Andi Kleen
2002-09-18 1:04 ` James Cleverdon
2002-09-19 18:02 ` Andrea Arcangeli
2002-09-20 11:04 ` Maciej W. Rozycki
2002-09-19 11:20 ` Mikael Pettersson
2002-09-19 13:27 ` Alan Cox
2002-09-19 13:39 ` Mikael Pettersson
2002-09-20 15:26 ` John Levon
2002-09-18 6:40 ` Vojtech Pavlik
2002-09-19 18:04 ` Andrea Arcangeli
[not found] <200209172020.g8HKKPF13227@eng2.beaverton.ibm.com>
2002-09-17 20:29 ` Fwd: " john stultz
2002-09-17 20:39 ` David S. Miller
2002-09-17 20:57 ` john stultz
2002-09-17 20:56 ` David S. Miller
2002-09-09 22:21 anton wilson
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=20020918015209.B31263@wotan.suse.de \
--to=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anton.wilson@camotion.com \
--cc=davem@redhat.com \
--cc=jamesclv@us.ibm.com \
--cc=johnstul@us.ibm.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