On Fri, Dec 09, 2022 at 02:32:15PM -0500, Boris Ostrovsky wrote:
>
> On 12/8/22 11:36 AM, Krister Johansen wrote:
> > + /*
> > +* As Dom0 is never moved, no penalty on using TSC there.
> > +*
> > +* If the guest has invariant tsc, then set xen_clocksource rating
> > +* below that
On 12/8/22 11:36 AM, Krister Johansen wrote:
+ /*
+* As Dom0 is never moved, no penalty on using TSC there.
+*
+* If the guest has invariant tsc, then set xen_clocksource rating
+* below that of the tsc so that the system prefers tsc instead. This
+
Kvm elects to use tsc instead of kvm-clock when it can detect that the
TSC is invariant.
(As of commit 7539b174aef4 ("x86: kvmguest: use TSC clocksource if
invariant TSC is exposed")).
Notable cloud vendors[1] and performance engineers[2] recommend that Xen
users preferentially select tsc over xe