From: Thomas Gleixner <tglx@linutronix.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Len Brown <lenb@kernel.org>, Andy Lutomirski <luto@kernel.org>,
X86 ML <x86@kernel.org>, Linux PM list <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>
Subject: Re: [PATCH 1/1] x86 TSC: set X86_FEATURE_TSC_RELIABLE, per CPUID
Date: Tue, 9 Jun 2015 10:15:31 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1506091014180.4133@nanos> (raw)
In-Reply-To: <CALCETrUvkBLQZXQYKs2nNTgUeBQvP1jntFPEkh0m6r_-CQt3-w@mail.gmail.com>
On Mon, 8 Jun 2015, Andy Lutomirski wrote:
> On Wed, Jun 3, 2015 at 12:03 PM, Len Brown <lenb@kernel.org> wrote:
> > If you boot this machine with "tsc=reliable", to disable the cpu_up
> > check_tsc_sync,
> > what happens? Does the run-time clocksource code detect the bogus TSC values?
> > If yes, how long does that take?
>
> They didn't detect it in the time I watched it.
Which is not surprising as the run-time check is disabled with the
reliable flag as well.
if (tsc_clocksource_reliable)
clocksource_tsc.flags &= ~CLOCK_SOURCE_MUST_VERIFY;
Thanks,
tglx
next prev parent reply other threads:[~2015-06-09 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-31 5:44 [PATCH 1/1] x86 TSC: set X86_FEATURE_TSC_RELIABLE, per CPUID Len Brown
2015-06-01 18:40 ` Andy Lutomirski
2015-06-02 0:45 ` Len Brown
2015-06-02 1:12 ` Andy Lutomirski
2015-06-03 19:03 ` Len Brown
2015-06-08 23:24 ` Andy Lutomirski
2015-06-09 8:15 ` Thomas Gleixner [this message]
2015-06-04 7:17 ` H. Peter Anvin
2015-06-06 16:12 ` Andy Lutomirski
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=alpine.DEB.2.11.1506091014180.4133@nanos \
--to=tglx@linutronix.de \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--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