Re: Re: system freeze when processor.ko is loaded during boot

["Jan Beulich" <JBeulich@novell.com>]

>>> On 04.04.11 at 11:22, "Jan Beulich" <JBeulich@novell.com> wrote:
> Haitao, while it is quite clear that with the current
> implementation we just can't use C states above C1 on CPUs
> that may halt the TSC in C2 or C3 *and* that don't allow
> writing the full TSC, this family/model based determination
> clearly isn't nice (and since it is a white list, it can't possibly be
> complete). An alternative would seem to be to probe for how
> TSC writes behave (thus at once covering eventual other
> vendors' CPUs that may have similar shortcomings). That of
> course would need to be done early, so that resetting the
> upper bits to zero wouldn't have any adverse effect. What
> do you think?

The probing itself seems to work fine. I'm confused by something
else though: synchronize_tsc_{master,slave}() execute their
loops (at boot or during hotplug) on any CPU that doesn't have
X86_FEATURE_TSC_RELIABLE, including such where TSC writes
don't really work (luckily I still haven't thrown out one that is
affected by this). What is the point of doing this synchronization
if we can happily live with it actually not working (Xen runs fine
on that box afaict)? c/s 21468:26c2922da53c is also not very
verbose about why this got (re-)added... Should the body
perhaps really only be run for X86_FEATURE_CONSTANT_TSC but
!X86_FEATURE_NONSTOP_TSC CPUs?

Jan