[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87y2py6466.fsf@nanos.tec.linutronix.de>
Date: Mon, 11 May 2020 14:34:41 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Radoslaw Biernacki <biernacki@...gle.com>,
Paul Menzel <pmenzel@...gen.mpg.de>
Cc: x86@...nel.org, Ross Zwisler <zwisler@...gle.com>,
Daniel Drake <drake@...lessm.com>,
Andy Lutomirski <luto@...nel.org>,
Borislav Petkov <bp@...en8.de>,
"H . Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Len Brown <len.brown@...el.com>,
Linux Upstreaming Team <linux@...lessm.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
Thorsten Leemhuis <regressions@...mhuis.info>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86/tsc: Use hard-coded crystal clock for Skylake mobile
Radoslaw Biernacki <biernacki@...gle.com> writes:
> We found that regression only on specific SKU which was used in one
> model of ChromeBook.
> What's interesting is that some other SKU is fine.
>
> The consequences of this are rather not trivial,
> so this was considered a quickfix and temporary till we develop
> something better.
> In contrast to ChromeOs, I know that there is no way of finding if
> there are in fact regressions on generic kernel in the field (this is
> SKU dependent),
> but we also think that this problem should be addressed in a better
> way (if possible).
Fix the BIOS to setup the CPUID/MSRs correctly?
Thanks,
tglx
Powered by blists - more mailing lists