x86/time: correctly honor late clearing of TSC related feature flags
authorJan Beulich <jbeulich@suse.com>
Tue, 7 Feb 2017 13:32:40 +0000 (14:32 +0100)
committerJan Beulich <jbeulich@suse.com>
Tue, 7 Feb 2017 13:32:40 +0000 (14:32 +0100)
commit63e1d01b8fd948b3e0fa3beea494e407668aa43b
treeccfb8734df70237b6e5b3114073a5d755de45d74
parent5fcf1c2516d253011b7c1001fe6a82e6c293f708
x86/time: correctly honor late clearing of TSC related feature flags

As such clearing of flags may have an impact on the selected rendezvous
function, defer the establishing of a rendezvous function other than
the initial default one (std) until after all APs have been brought up.

But don't allow such feature flags to be cleared during CPU hotplug:
Platform and local system times may have diverged significantly by
then, potentially causing noticeably (even if only temporary) strange
behavior. As we're anyway expecting only sufficiently similar CPUs to
appear during hotplug, this shouldn't be introducing new limitations.

Reported-by: Joao Martins <joao.m.martins@oracle.com>
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>
xen/arch/x86/time.c