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
| ||
|
Date: Fri, 24 Jan 2020 12:55:54 +0100 From: Thomas Gleixner <tglx@...utronix.de> To: Hans de Goede <hdegoede@...hat.com>, Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, vipul kumar <vipulk0511@...il.com> Cc: Daniel Lezcano <daniel.lezcano@...aro.org>, linux-kernel@...r.kernel.org, Stable <stable@...r.kernel.org>, Srikanth Krishnakar <Srikanth_Krishnakar@...tor.com>, Cedric Hombourger <Cedric_Hombourger@...tor.com>, x86@...nel.org, Len Brown <len.brown@...el.com>, Vipul Kumar <vipul_kumar@...tor.com> Subject: Re: [v3] x86/tsc: Unset TSC_KNOWN_FREQ and TSC_RELIABLE flags on Intel Bay Trail SoC Hans, Hans de Goede <hdegoede@...hat.com> writes: > On 1/24/20 9:35 AM, Thomas Gleixner wrote: >> Where does that number come from? Just math? > > Yes just math, but perhaps the Intel folks can see if they can find some > datasheet to back this up ? Can you observe the issue on one of the machines in your zoo as well? Thanks, tglx
Powered by blists - more mailing lists