From: Bin Gao Date: Tue, 15 Nov 2016 20:27:23 +0000 (-0800) Subject: x86/tsc: Mark Intel ATOM_GOLDMONT TSC reliable X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=4635fdc696a8e89eead3ea1712ae6ada38538d40;p=GitHub%2Fmoto-9609%2Fandroid_kernel_motorola_exynos9610.git x86/tsc: Mark Intel ATOM_GOLDMONT TSC reliable On Intel GOLDMONT Atom SoC TSC is the only available clocksource, so there is no way to do software calibration or have a watchdog clocksource for it. Software calibration is already disabled via the TSC_KNOWN_FREQ flag, but the watchdog requirement still persists, so such systems cannot switch to high resolution/nohz mode. Mark it reliable, so it becomes usable. Hardware teams confirmed that this is safe on that SoC. Signed-off-by: Bin Gao Cc: Peter Zijlstra Link: http://lkml.kernel.org/r/1479241644-234277-4-git-send-email-bin.gao@linux.intel.com Signed-off-by: Thomas Gleixner --- diff --git a/arch/x86/kernel/tsc.c b/arch/x86/kernel/tsc.c index e58c31959666..f4dfdaa6633c 100644 --- a/arch/x86/kernel/tsc.c +++ b/arch/x86/kernel/tsc.c @@ -709,6 +709,13 @@ unsigned long native_calibrate_tsc(void) */ setup_force_cpu_cap(X86_FEATURE_TSC_KNOWN_FREQ); + /* + * For Atom SoCs TSC is the only reliable clocksource. + * Mark TSC reliable so no watchdog on it. + */ + if (boot_cpu_data.x86_model == INTEL_FAM6_ATOM_GOLDMONT) + setup_force_cpu_cap(X86_FEATURE_TSC_RELIABLE); + return crystal_khz * ebx_numerator / eax_denominator; }