From: Andi Kleen <andi@firstfloor.org>
To: Luming Yu <luming.yu@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC patch] reset TSC at the begining of check_tsc_warp
Date: Tue, 02 Jun 2009 09:54:44 +0200 [thread overview]
Message-ID: <87my8rcbp7.fsf@basil.nowhere.org> (raw)
In-Reply-To: <3877989d0906010201j438a08a8x559f62b0aed40696@mail.gmail.com> (Luming Yu's message of "Mon, 1 Jun 2009 17:01:53 +0800")
Luming Yu <luming.yu@gmail.com> writes:
> Hello,
>
> Without this patch, we always get kernel warning that TSC warp between CPUs,
> and TSC is marked unstable due to check_tsc_sync_source failed if the CPUs
> have the problem of not-synced initial TSC.
>
> It hurts CPUs with constant-tsc feature, but with unsynced initial TSC value...
>
> The downside is we could break perfect synced TSC with this patch.
s/could/will definitely/
So you're hurting the good systems for one buggy box. I don't think
that's a good idea.
Possible alternatives:
- black list that system with DMI
- try to detect it by checking constant_tsc and still unsynchronized TSC
- just give up and say the system won't be able to use TSC unless the BIOS
fixes its act.
The third option is probably not the worst.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-06-02 7:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 9:01 [RFC patch] reset TSC at the begining of check_tsc_warp Luming Yu
2009-06-01 23:10 ` Frans Pop
2009-06-02 7:05 ` Luming Yu
2009-06-02 7:54 ` Andi Kleen [this message]
2009-06-02 8:28 ` Luming Yu
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=87my8rcbp7.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@gmail.com \
/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