From: Lee Revell <rlrevell@joe-job.com>
To: Albert Cahalan <acahalan@gmail.com>
Cc: linux-kernel@vger.kernel.org, s0348365@sms.ed.ac.uk,
safemode@comcast.net
Subject: Re: athlon 64 dual core tsc out of sync
Date: Sat, 04 Feb 2006 20:00:42 -0500 [thread overview]
Message-ID: <1139101243.2791.78.camel@mindpipe> (raw)
In-Reply-To: <787b0d920602041224p660911b5mc4d639581736e96f@mail.gmail.com>
On Sat, 2006-02-04 at 15:24 -0500, Albert Cahalan wrote:
> There have been far too many other problems with i386 timekeeping as
> well. Really, it's crazy to not use the pmtmr if the pmtmr is
> available. The next best choice would be HPET. After that, pre-SMM
> systems should count clock ticks and post-SMM systems should read the
> RTC or PIT registers. Until we accept this, we'll always be suffering
> clock problems.
Well, I wouldn't say it's crazy - the TSC is several orders of magnitude
cheaper than the PM timer, and the only common hardware where it's
completely useless are Athlon X2 systems.
Fortunately there's a solution in the works - John Stultz's gettimeofday
rework. Try the -rt tree for a preview.
Lee
next prev parent reply other threads:[~2006-02-05 1:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-04 20:24 athlon 64 dual core tsc out of sync Albert Cahalan
2006-02-05 1:00 ` Lee Revell [this message]
2006-02-05 1:45 ` Albert Cahalan
2006-02-05 2:08 ` Lee Revell
2006-02-05 3:02 ` Ed Sweetman
2006-02-05 5:08 ` Alistair John Strachan
2006-02-05 2:24 ` Lee Revell
2006-02-05 5:06 ` Alistair John Strachan
-- strict thread matches above, loose matches on Subject: below --
2006-02-04 2:10 Ed Sweetman
2006-02-04 19:03 ` Lee Revell
2006-02-04 19:52 ` Alistair John Strachan
2006-02-04 21:55 ` Ed Sweetman
2006-02-04 19:16 ` Lee Revell
2006-02-05 16:32 ` Andi Kleen
2006-02-06 1:12 ` Ed Sweetman
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=1139101243.2791.78.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=acahalan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s0348365@sms.ed.ac.uk \
--cc=safemode@comcast.net \
/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.