2017-07-10 15:25+0200, Radim Krčmář: > 2017-06-28 13:55+0300, Denis Plotnikov: > > Get rid of complex shadow monotonic timekeeper support in KVM. > > Extend and use timekeeper infrastructure instead. > > > > Make kvm-clock stable in L2 using the changed timekeeper > > I see this patch as two logical changes: > > 1) refactoring that drops host time caching (gtod) > 2) stable kvmclock for L2 when L1 is using kvmclock > > Doing it in two patches would definitely be nicer and would allow us to > focus on the (less controversial) L2 enablement. I just realized that (2) has more complex dependency on (1): we'd need extra code to get boot_ns from TSC via kvmclock, so deciding the refactoring first was a good call.
