[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1807032257330.1816@nanos.tec.linutronix.de>
Date: Tue, 3 Jul 2018 22:59:31 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Pavel Tatashin <pasha.tatashin@...cle.com>
cc: Steven Sistare <steven.sistare@...cle.com>,
Daniel Jordan <daniel.m.jordan@...cle.com>,
linux@...linux.org.uk, Martin Schwidefsky <schwidefsky@...ibm.com>,
Heiko Carstens <heiko.carstens@...ibm.com>,
John Stultz <john.stultz@...aro.org>, sboyd@...eaurora.org,
x86@...nel.org, LKML <linux-kernel@...r.kernel.org>,
mingo@...hat.com, "H. Peter Anvin" <hpa@...or.com>,
douly.fnst@...fujitsu.com, Peter Zijlstra <peterz@...radead.org>,
Prarit Bhargava <prarit@...hat.com>, feng.tang@...el.com,
Petr Mladek <pmladek@...e.com>, gnomes@...rguk.ukuu.org.uk,
linux-s390@...r.kernel.org, andriy.shevchenko@...ux.intel.com,
boris.ostrovsky@...cle.com, pbonzini@...hat.com
Subject: Re: [PATCH v12 09/11] x86/tsc: prepare for early sched_clock
On Fri, 29 Jun 2018, Pavel Tatashin wrote:
> On 18-06-29 09:30:10, Thomas Gleixner wrote:
> For now, in my series, I would like check in tsc_early_init() if we are
> running xen, and set tsc_khz to 0 if so. Later in tsc_init() we will get
> a proper calibration. The question is how to make this check least
> intrusive.
By not having it at all. Talk to the XEN folks (IIRC there are a few
coworkers of you involved with XEN).
Thanks,
tglx
Powered by blists - more mailing lists