From: Pasha Tatashin <pasha.tatashin@oracle.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org, mingo@redhat.com,
tglx@linutronix.de, hpa@zytor.com
Subject: Re: [v1 0/9] Early boot time stamps for x86
Date: Wed, 22 Mar 2017 20:02:34 -0400 [thread overview]
Message-ID: <e8e2a870-fea9-54d8-3107-928032911df3@oracle.com> (raw)
In-Reply-To: <20170322202712.5d6l7klwucnfhucm@hirez.programming.kicks-ass.net>
On 2017-03-22 16:27, Peter Zijlstra wrote:
> On Wed, Mar 22, 2017 at 04:24:16PM -0400, Pavel Tatashin wrote:
>> Last week I sent out patches to enable early boot time stamp on SPARC, that
>> work is now under review:
>> http://www.spinics.net/lists/sparclinux/msg17372.html
>>
>> This is continuation for that work, but adding early boot time stamps
>> support for x86 machines.
>
> *groan*, so we get an even bigger trainwreck when TSC is fscked?
>
Hi Peter,
I am not sure what you mean. If tsc is not reliable, the worst case is
that during early boot the timestamps won't be as accurate as the
timestamps that are enabled once we initialize some other clock sources.
In either way, if you look at the way I enabled early timestamps, it is
really narrowed down to work only on modern hardware with stable tsc.
(Nehalem and later)
Thank you,
Pasha
next prev parent reply other threads:[~2017-03-23 0:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 20:24 Pavel Tatashin
2017-03-22 20:24 ` [v1 1/9] sched/clock: broken stable to unstable transfer Pavel Tatashin
2017-03-27 10:27 ` [tip:sched/urgent] sched/clock: Fix " tip-bot for Pavel Tatashin
2017-03-22 20:24 ` [v1 2/9] sched/clock: interface to allow timestamps early in boot Pavel Tatashin
2017-03-22 20:24 ` [v1 3/9] x86/cpu: determining x86 vendor early Pavel Tatashin
2017-03-22 20:24 ` [v1 4/9] x86/tsc: early MSR-based CPU/TSC frequency discovery Pavel Tatashin
2017-03-22 20:24 ` [v1 5/9] x86/tsc: disable early messages from quick_pit_calibrate Pavel Tatashin
2017-03-22 20:24 ` [v1 6/9] x86/tsc: use cpuid to determine TSC frequency Pavel Tatashin
2017-03-22 20:24 ` [v1 7/9] x86/tsc: use cpuid to determine CPU frequency Pavel Tatashin
2017-03-22 20:24 ` [v1 8/9] x86/tsc: tsc early Pavel Tatashin
2017-03-24 5:38 ` kbuild test robot
2017-03-22 20:24 ` [v1 9/9] x86/tsc: use " Pavel Tatashin
2017-03-22 20:27 ` [v1 0/9] Early boot time stamps for x86 Peter Zijlstra
2017-03-23 0:02 ` Pasha Tatashin [this message]
2017-03-22 20:28 ` Peter Zijlstra
2017-03-22 23:59 ` Pasha Tatashin
2017-03-23 10:56 ` Thomas Gleixner
2017-03-23 14:39 ` Pasha Tatashin
2017-03-23 18:40 ` Thomas Gleixner
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=e8e2a870-fea9-54d8-3107-928032911df3@oracle.com \
--to=pasha.tatashin@oracle.com \
--cc=hpa@zytor.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®