From: Gratian Crisan <gratian.crisan@ni.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Gratian Crisan <gratian.crisan@ni.com>,
Josh Hunt <joshhunt00@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
<x86@kernel.org>, Borislav Petkov <bp@alien8.de>,
Josh Cartwright <joshc@ni.com>, <gratian@gmail.com>
Subject: Re: [RFC PATCH] tsc: synchronize TSCs on buggy Intel Xeon E5 CPUs with offset error
Date: Tue, 17 Nov 2015 10:38:21 -0600 [thread overview]
Message-ID: <87r3jofuo2.fsf@spline.amer.corp.natinst.com> (raw)
In-Reply-To: <20151113204338.GA9928@worktop.ger.corp.intel.com>
Peter Zijlstra writes:
> On Wed, Nov 11, 2015 at 09:41:25AM -0600, Gratian Crisan wrote:
>> I also wrote a small C utility[1], with a bit of code borrowed from the
>> kernel, for reading the TSC on all CPUs. It starts a high priority
>> thread per CPU, tries to synchronize them and prints out the TSC values
>> and their offset with regards to CPU0.
>> It can be called from a SysV init shell script[2] at the beginning of
>> the boot process and right before a reboot to save the values in a file.
>
> Could you also read and print TSC_ADJUST (msr 0x3b) ? This would tell us
> if for example your BIOS messed it up.
Good call on the TSC_ADJUST. The BIOS seems to set it for CPU0 but not
for any of the other ones. I'll bug our BIOS guys about it.
Here's how the data looks after a couple reboots:
stop : 127385698358[0] 741784252175365[741656866477007] 741784252175432[741656866477074] 741784252175471[741656866477113] 741784252175349[741656866476991] 741784252175458[741656866477100] 741784252175285[741656866476927] 741784252175501[741656866477143]
TSC_ADJUST: -741656866477048 0 0 0 0 0 0 0
start : 47601069657[0] 741849504816842[741801903747185] 741849504816884[741801903747227] 741849504817004[741801903747347] 741849504817113[741801903747456] 741849504817051[741801903747394] 741849504816746[741801903747089] 741849504816962[741801903747305]
TSC_ADJUST: -741801903747272 0 0 0 0 0 0 0
stop : 127495422447[0] 741929399169793[741801903747346] 741929399169821[741801903747374] 741929399169739[741801903747292] 741929399169767[741801903747320] 741929399169657[741801903747210] 741929399169612[741801903747165] 741929399169679[741801903747232]
TSC_ADJUST: -741801903747272 0 0 0 0 0 0 0
start : 47522880051[0] 741994508088208[741946985208157] 741994508088258[741946985208207] 741994508088305[741946985208254] 741994508088110[741946985208059] 741994508088052[741946985208001] 741994508088020[741946985207969] 741994508087930[741946985207879]
TSC_ADJUST: -741946985208111 0 0 0 0 0 0 0
Thanks a lot for helping with this,
-Gratian
next prev parent reply other threads:[~2015-11-17 16:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 19:59 gratian.crisan
2015-11-09 22:02 ` Peter Zijlstra
[not found] ` <CAKA=qzarnUUmZb7DQE+u0Dei3F+FQNoL2bak_-dV9D9+3L=itQ@mail.gmail.com>
2015-11-10 18:27 ` Josh Hunt
2015-11-10 19:47 ` Gratian Crisan
2015-11-10 20:41 ` Josh Hunt
2015-11-11 15:41 ` Gratian Crisan
2015-11-13 20:43 ` Peter Zijlstra
2015-11-17 16:38 ` Gratian Crisan [this message]
2015-11-19 19:04 ` Gratian Crisan
2015-11-13 21:13 ` Dave Hansen
2015-11-17 16:49 ` Gratian Crisan
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=87r3jofuo2.fsf@spline.amer.corp.natinst.com \
--to=gratian.crisan@ni.com \
--cc=bp@alien8.de \
--cc=gratian@gmail.com \
--cc=hpa@zytor.com \
--cc=joshc@ni.com \
--cc=joshhunt00@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®