On 01/12/2017 14:13, Vitaly Kuznetsov wrote: > Currently, KVM passes PVCLOCK_TSC_STABLE_BIT to its guests when running in > so called 'masterclock' mode and this is only possible when the clocksource > on the host is TSC. When running nested on Hyper-V we're using a different > clocksource in L1 (Hyper-V TSC Page) which can actually be used for > masterclock. This series brings the required support. > > Making KVM work with TSC page clocksource is relatively easy, it is done in > PATCH 5 of the series. All the rest is required to support L1 migration > when TSC frequency changes, we use a special feature from Hyper-V to do > the job. This looks great. If the Hyper-V folks can provide a topic branch with patches 1-4 in it, we can merge it. Thanks, Paolo
