Paolo Bonzini e3fd9a93a1 kvm: kvmclock: let KVM_GET_CLOCK return whether the master clock is in use ... Userspace can read the exact value of kvmclock by reading the TSC and fetching the timekeeping parameters out of guest memory. This however is brittle and not necessary anymore with KVM 4.11. Provide a mechanism that lets userspace know if the new KVM_GET_CLOCK semantics are in effect, and---since we are at it---if the clock is stable across all VCPUs. Cc: Radim Krčmář <rkrcmar@redhat.com> Cc: Marcelo Tosatti <mtosatti@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>		2016-11-19 19:04:16 +01:00
..
arm
devices	KVM: arm64: Require in-kernel irqchip for PMU support	2016-09-27 18:57:07 +02:00
00-INDEX
api.txt	kvm: kvmclock: let KVM_GET_CLOCK return whether the master clock is in use	2016-11-19 19:04:16 +01:00
cpuid.txt
hypercalls.txt
locking.txt	KVM: document lock orders	2016-10-27 11:35:47 +02:00
mmu.txt	One of the largest releases for KVM... Hardly any generic improvement,	2016-03-16 09:55:35 -07:00
msr.txt
nested-vmx.txt
ppc-pv.txt
review-checklist.txt
s390-diag.txt
timekeeping.txt