From: Steven Rostedt <rostedt@goodmis.org>
To: Luming Yu <luming.yu@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
John Stultz <johnstul@us.ibm.com>
Subject: Re: what is the better method to do tsc synchronized check?
Date: Thu, 17 Mar 2011 00:10:01 -0400 [thread overview]
Message-ID: <20110317041001.GC14675@home.goodmis.org> (raw)
In-Reply-To: <AANLkTi=HB7s-VpMAZmNBPgvQadtN9tg91pFY-=atAWsM@mail.gmail.com>
[ Added Cc's of people that might help you. ]
-- Steve
On Wed, Mar 16, 2011 at 10:56:25PM -0400, Luming Yu wrote:
> Hi there,
>
> I tested two different methods to do TSC sync check on a Sandy Bridge system.
> The first TSC sync check method is from upstream -38-rc that considers
> TSC is synced.
> The second TSC sync check method is from a 2.6.18 based kernel that
> considers TSC
> is NOT synced on the Sandy Bridge system. (I modified sync_tsc() to
> just test (not modify TSC) on
> the cpu being tested.)
>
> [root@intel-sugarbay-DO-01 kernel]# dmesg | grep -i synchroniz
> CPU 1: synchronized TSC with CPU 0 (last diff 29 cycles, maxerr 276 cycles)
> CPU 2: synchronized TSC with CPU 0 (last diff 32 cycles, maxerr 280 cycles)
> CPU 3: synchronized TSC with CPU 0 (last diff 31 cycles, maxerr 284 cycles)
>
> Do you guy think we need to take 2.6.18-based tsc sync testing method
> rather than the current one in upstream?
>
> Any inputs are appreciated.
>
>
> Thanks
> Luming
> --
prev parent reply other threads:[~2011-03-17 4:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 2:56 Luming Yu
2011-03-17 4:10 ` Steven Rostedt [this message]
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=20110317041001.GC14675@home.goodmis.org \
--to=rostedt@goodmis.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@gmail.com \
--cc=tglx@linutronix.de \
/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®