From: Peter Zijlstra <peterz@infradead.org>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Paolo Bonzini <pbonzini@redhat.com>,
Radim Krcmar <rkrcmar@redhat.com>,
Wanpeng Li <kernellwp@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, X86 ML <x86@kernel.org>,
Matt Rickard <matt@softrans.com.au>,
Stephen Boyd <sboyd@kernel.org>,
John Stultz <john.stultz@linaro.org>,
Florian Weimer <fweimer@redhat.com>,
KY Srinivasan <kys@microsoft.com>,
devel@linuxdriverproject.org,
Linux Virtualization <virtualization@lists.linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>, Juergen Gross <jgross@suse.com>
Subject: Re: [patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
Date: Thu, 4 Oct 2018 10:11:00 +0200 [thread overview]
Message-ID: <20181004081100.GI19272@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <87k1mycfju.fsf@vitty.brq.redhat.com>
On Thu, Oct 04, 2018 at 09:54:45AM +0200, Vitaly Kuznetsov wrote:
> I was hoping to hear this from you :-) If I am to suggest how we can
> move forward I'd propose:
> - Check if pure TSC can be used on SkyLake+ systems (where TSC scaling
> is supported).
> - Check if non-masterclock mode is still needed. E.g. HyperV's TSC page
> clocksource is a single page for the whole VM, not a per-cpu thing. Can
> we think that all the buggy hardware is already gone?
No, and it is not the hardware you have to worry about (mostly), it is
the frigging PoS firmware people put on it.
Ever since Nehalem TSC is stable (unless you get to >4 socket systems,
after which it still can be, but bets are off). But even relatively
recent systems fail the TSC sync test because firmware messes it up by
writing to either MSR_TSC or MSR_TSC_ADJUST.
But the thing is, if the TSC is not synced, you cannot use it for
timekeeping, full stop. So having a single page is fine, it either
contains a mult/shift that is valid, or it indicates TSC is messed up
and you fall back to something else.
There is no inbetween there.
For sched_clock we can still use the global page, because the rate will
still be the same for each cpu, it's just offset between CPUs and the
code compensates for that.
next prev parent reply other threads:[~2018-10-04 8:21 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 12:50 [patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support Thomas Gleixner
2018-09-14 12:50 ` [patch 01/11] clocksource: Provide clocksource_arch_init() Thomas Gleixner
2018-09-14 12:50 ` [patch 02/11] x86/time: Implement clocksource_arch_init() Thomas Gleixner
2018-09-14 15:45 ` Vitaly Kuznetsov
2018-09-15 6:05 ` Thomas Gleixner
2018-09-14 12:50 ` [patch 03/11] x86/vdso: Enforce 64bit clocksource Thomas Gleixner
2018-09-14 12:50 ` [patch 04/11] x86/vdso: Use unsigned int consistently for vsyscall_gtod_data::seq Thomas Gleixner
2018-09-14 12:50 ` [patch 05/11] x86/vdso: Introduce and use vgtod_ts Thomas Gleixner
2018-09-14 12:50 ` [patch 06/11] x86/vdso: Collapse high resolution functions Thomas Gleixner
2018-09-14 12:50 ` [patch 07/11] x86/vdso: Collapse coarse functions Thomas Gleixner
2018-09-14 12:50 ` [patch 08/11] x86/vdso: Replace the clockid switch case Thomas Gleixner
2018-09-14 12:50 ` [patch 09/11] x86/vdso: Simplify the invalid vclock case Thomas Gleixner
2018-09-17 19:25 ` Andy Lutomirski
2018-09-17 20:12 ` John Stultz
2018-09-18 7:52 ` Thomas Gleixner
2018-09-18 8:30 ` Peter Zijlstra
2018-09-18 8:52 ` Thomas Gleixner
2018-09-18 10:06 ` Thomas Gleixner
2018-09-18 10:41 ` Thomas Gleixner
2018-09-18 12:48 ` Peter Zijlstra
2018-09-18 13:23 ` Thomas Gleixner
2018-09-18 13:38 ` Peter Zijlstra
2018-09-18 15:52 ` Thomas Gleixner
2018-09-27 14:41 ` Thomas Gleixner
2018-09-18 14:01 ` Andy Lutomirski
2018-09-18 22:46 ` Thomas Gleixner
2018-09-18 23:03 ` Andy Lutomirski
2018-09-18 23:16 ` Thomas Gleixner
2018-09-27 14:36 ` Thomas Gleixner
2018-09-27 14:39 ` Andy Lutomirski
2018-09-19 9:08 ` Rasmus Villemoes
2018-09-19 13:29 ` Thomas Gleixner
2018-09-14 12:50 ` [patch 10/11] x86/vdso: Move cycle_last handling into the caller Thomas Gleixner
2018-09-14 15:26 ` Vitaly Kuznetsov
2018-09-14 12:50 ` [patch 11/11] x66/vdso: Add CLOCK_TAI support Thomas Gleixner
2018-09-14 14:04 ` Andy Lutomirski
2018-09-14 14:27 ` Thomas Gleixner
2018-09-14 14:59 ` Andy Lutomirski
2018-09-16 9:39 ` Thomas Gleixner
2018-09-14 12:56 ` [patch 00/11] x86/vdso: Cleanups, simmplifications and " Florian Weimer
2018-09-14 13:05 ` Thomas Gleixner
2018-09-14 13:06 ` Florian Weimer
2018-09-14 13:19 ` Thomas Gleixner
2018-09-14 13:09 ` Peter Zijlstra
2018-09-14 14:22 ` Arnd Bergmann
2018-09-17 13:00 ` Thomas Gleixner
2018-09-24 21:08 ` Arnd Bergmann
2018-10-03 5:15 ` Andy Lutomirski
2018-10-03 9:22 ` Vitaly Kuznetsov
2018-10-03 10:20 ` Andy Lutomirski
2018-10-03 12:01 ` Vitaly Kuznetsov
2018-10-03 14:20 ` Andy Lutomirski
2018-10-03 15:10 ` Thomas Gleixner
2018-10-03 16:18 ` Andy Lutomirski
2018-10-03 19:06 ` Marcelo Tosatti
2018-10-04 7:54 ` Vitaly Kuznetsov
2018-10-04 8:11 ` Peter Zijlstra [this message]
2018-10-04 14:00 ` Andy Lutomirski
2018-10-04 19:31 ` Peter Zijlstra
2018-10-04 20:05 ` Andy Lutomirski
2018-10-04 22:15 ` Andy Lutomirski
2018-10-06 20:27 ` Marcelo Tosatti
2018-10-06 22:28 ` Andy Lutomirski
2018-10-08 15:26 ` Marcelo Tosatti
2018-10-08 17:38 ` Andy Lutomirski
2018-10-08 19:36 ` Marcelo Tosatti
2018-10-09 20:09 ` Andy Lutomirski
2018-10-11 22:27 ` Marcelo Tosatti
2018-10-11 23:00 ` Andy Lutomirski
2018-10-15 13:39 ` Marcelo Tosatti
2018-10-06 20:49 ` Marcelo Tosatti
2018-10-04 12:00 ` Paolo Bonzini
2018-10-04 14:04 ` Andy Lutomirski
2018-10-05 21:18 ` Marcelo Tosatti
2018-10-03 19:00 ` Marcelo Tosatti
2018-10-03 19:05 ` [patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support\ Marcelo Tosatti
2018-10-03 22:32 ` [patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support Andy Lutomirski
2018-10-04 16:37 ` Marcelo Tosatti
2018-10-04 17:08 ` Andy Lutomirski
2018-10-04 17:28 ` Vitaly Kuznetsov
2018-10-04 20:32 ` 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=20181004081100.GI19272@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=arnd@arndb.de \
--cc=devel@linuxdriverproject.org \
--cc=fweimer@redhat.com \
--cc=jgross@suse.com \
--cc=john.stultz@linaro.org \
--cc=kernellwp@gmail.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=matt@softrans.com.au \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=vkuznets@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).