Re: [v3] x86/tsc: Unset TSC_KNOWN_FREQ and TSC_RELIABLE flags on Intel Bay Trail SoC

[Thomas Gleixner]

Vipul,

Vipul Kumar <vipulk0511@xxxxxxxxx> writes:

> commit f3a02ecebed7 ("x86/tsc: Set TSC_KNOWN_FREQ and TSC_RELIABLE
> flags on Intel Atom SoCs"), is setting TSC_KNOWN_FREQ and TSC_RELIABLE
> flags for Soc's which is causing time drift on Valleyview/Bay trail Soc.

This lacks any form of information what the difference is. I asked about
that before and got no answer.

> This patch introduces a new macro to skip these flags.

git grep 'This patch' Documentation/process/submitting-patches.rst

> Signed-off-by: Vipul Kumar <vipul_kumar@xxxxxxxxxx>
> Cc: stable@xxxxxxxxxxxxxxx

That stable tag is useless as you already have identied the commit which
is "Fixed" by your patch.

>  
> +config X86_FEATURE_TSC_UNKNOWN_FREQ
> +	bool "Support to skip tsc known frequency flag"
> +	help
> +	  Include support to skip X86_FEATURE_TSC_KNOWN_FREQ flag
> +
> +	  X86_FEATURE_TSC_KNOWN_FREQ flag is causing time-drift on Valleyview/
> +	  Baytrail SoC.
> +	  By selecting this option, user can skip X86_FEATURE_TSC_KNOWN_FREQ
> +	  flag to use refine tsc freq calibration.

This is exactly the same problem as before. How does anyone aside of you
know whether to enable this or not?

And if someone enables this option then _ALL_ platforms which utilize
cpu_khz_from_msr() are affected. How is that any different from your
previous approach? This works on local kernels where you build for a
specific platform and you know exactly what you're doing, but not for
general consumption. What should a distro do with this option?

Thanks,

        tglx