On Tue, 19 Jan 2021 at 02:27, Paolo Bonzini <[email protected]> wrote: > > On 15/01/21 02:15, Wanpeng Li wrote: > >> The comment above should probably be updated as it is not clear why we > >> check kvm_clock.vdso_clock_mode here. Actually, I would even suggest we > >> introduce a 'kvmclock_tsc_stable' global instead to avoid this indirect > >> check. > > I prefer to update the comment above, assign vsyscall pvclock data > > pointer iff kvmclock vsyscall is enabled. > > Are you going to send v2?
Yes. :) https://lore.kernel.org/kvm/[email protected]/ Wanpeng
