From: "H. Peter Anvin" <hpa@zytor.com>
To: "\"Paul Rolland (ポール・ロラン)\"" <rol@witbe.net>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: constant_tsc and TSC unstable
Date: Thu, 29 Nov 2007 23:04:40 -0800 [thread overview]
Message-ID: <474FB608.4030508@zytor.com> (raw)
In-Reply-To: <20071130075932.7f1f0974@tux.DEF.witbe.net>
Paul Rolland (ポール・ロラン) wrote:
>
>> Note that once TSC is disabled (it's using "jiffies" as far
>> as I can see), ntpd constantly speeds up and slows down the
>> clock, it jumps +/- 0.5sec every several minutes or hours -
>> I guess that's when ntpd process gets moved from one core
>> to another for whatever reason. And an interesting thing
>> is that with 64bits kernel this TSC problem does not occur
>> on this very machine.
> Hmmmm.... That could make it a problem related to kernel rather than CPU.
>
>> Something similar is reported on AMD X2 64 machines as well --
>> can't check right now.
> If I recall correctly, issues with AMD X2 where related to TSC being
> independant for each core and not constant (speed depending of C state).
> But the reason I raise the issue is that the Core2 reports constant TSC,
> so there is (IMHO) no reason for that.
>
Well, "constant" doesn't mean "synchronized", but it might very well be
that the Core2 could really benefit from synchronizing the TSCs manually
like we used to.
On the other hand, I notice that most of the TSC warp values are
relatively close to 2^32, so this could be a specific bug.
-hpa
next prev parent reply other threads:[~2007-11-30 7:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 16:11 constant_tsc and TSC unstable Paul Rolland
2007-11-29 19:04 ` H. Peter Anvin
2007-11-29 21:26 ` Michael Tokarev
2007-11-30 6:59 ` Paul Rolland
2007-11-30 7:04 ` H. Peter Anvin [this message]
2007-11-29 21:36 ` Patrick McHardy
2007-11-29 23:29 ` Pallipadi, Venkatesh
2007-11-30 6:52 ` Paul Rolland (ポール・ロラン)
2007-12-06 0:35 ` Pallipadi, Venkatesh
2007-11-30 0:30 ` Frans Pop
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=474FB608.4030508@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=rol@witbe.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox