Re: [PATCH 1/2] x86/tsc: use CPUID.0x16 to calculate missing crystal frequency

2019-04-24 Thread Daniel Drake
On Tue, Apr 23, 2019 at 5:08 PM Peter Zijlstra wrote: > Well, SKX isn't exactly 'missing'; it would be very good if we can > confirm the new code is still correct under the below mentioned > conditions. > > commit b511203093489eb1829cb4de86e8214752205ac6 > Author: Len Brown > Date: Fri Dec 22

Re: [PATCH 1/2] x86/tsc: use CPUID.0x16 to calculate missing crystal frequency

2019-04-23 Thread Peter Zijlstra
On Mon, Apr 22, 2019 at 06:15:25PM +0800, Daniel Drake wrote: > Additionally, crystal clock frequency for platforms that were missing > from the list (e.g. SKYLAKE_X) will now be provided. Well, SKX isn't exactly 'missing'; it would be very good if we can confirm the new code is still correct

[PATCH 1/2] x86/tsc: use CPUID.0x16 to calculate missing crystal frequency

2019-04-22 Thread Daniel Drake
native_calibrate_tsc() had a hardcoded table of Intel CPU families and crystal clock, but we have found that it is possible to calculate the crystal clock speed, and this is preferred to a hardcoded table. Where crystal clock frequency was not reported by CPUID.0x15, use CPUID.0x16 data to