linux-kernel - Re: [PATCH] x86/tsc: Use hard-coded crystal clock for Skylake mobile

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 11 May 2020 17:39:23 +0200
From:   Radoslaw Biernacki <biernacki@...gle.com>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     Paul Menzel <pmenzel@...gen.mpg.de>, 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

On Mon, May 11, 2020 at 2:34 PM Thomas Gleixner <tglx@...utronix.de> wrote:
>
> 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

Yes of course, but "if possible" might mean we would not be able to
fix the BIOS.
Anyway, let me see what actually can be done.