From: Andi Kleen <andi@firstfloor.org>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH] Allow Intel platforms to declare unsynchronized TSC to kernel
Date: Mon, 29 Mar 2010 12:47:34 +0200 [thread overview]
Message-ID: <87oci776bd.fsf@basil.nowhere.org> (raw)
In-Reply-To: <4BB07636.7010708@jp.fujitsu.com> (Hidetoshi Seto's message of "Mon, 29 Mar 2010 18:43:18 +0900")
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com> writes:
> (2010/03/29 16:46), Andi Kleen wrote:
>> Andi Kleen <andi@firstfloor.org> writes:
>>
>>> Allow Intel platforms to declare unsynchronized TSC to kernel
>>>
>>> [This came out of a private discussion with Linus last week]
>>
>> Ping? Please review this patch.
>>
>> -Andi
>
> Does "constant" implicitly means "synchronized"?
Yes it does for the CPUID bit.
> Following commit tells us that there could be
> "constant-but-unsynchronized TSC":
> 6c56ccecf05fafe100ab4ea94f6fccbf5ff00db7
>> So, reenable TSC sync test even on constant and non-stop TSC systems.
First the platform is supposed to clear in this case and when it
doesn't the later check catches it anyways.
BTW all the things you're mentioning are not actually changed by my
patch. In this regard it behaves the same as before. I don't think
the patch description has to describe things it does not change
or be a general tutorial on TSCs.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2010-03-29 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 5:32 [PATCH] Allow Intel platforms to declare unsynchronized TSC to kernel Andi Kleen
2010-03-29 7:46 ` Andi Kleen
2010-03-29 9:43 ` Hidetoshi Seto
2010-03-29 10:47 ` Andi Kleen [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=87oci776bd.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=tglx@linutronix.de \
--cc=torvalds@osdl.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