diff options
author | Marcelo Tosatti <mtosatti@redhat.com> | 2012-11-28 02:29:01 +0100 |
---|---|---|
committer | Marcelo Tosatti <mtosatti@redhat.com> | 2012-11-28 02:29:13 +0100 |
commit | d828199e84447795c6669ff0e6c6d55eb9beeff6 (patch) | |
tree | c11fc58c50234ddf06f1c4ca98a4115c8fe8ac2f /arch/x86/kvm/svm.c | |
parent | KVM: x86: notifier for clocksource changes (diff) | |
download | linux-d828199e84447795c6669ff0e6c6d55eb9beeff6.tar.xz linux-d828199e84447795c6669ff0e6c6d55eb9beeff6.zip |
KVM: x86: implement PVCLOCK_TSC_STABLE_BIT pvclock flag
KVM added a global variable to guarantee monotonicity in the guest.
One of the reasons for that is that the time between
1. ktime_get_ts(×pec);
2. rdtscll(tsc);
Is variable. That is, given a host with stable TSC, suppose that
two VCPUs read the same time via ktime_get_ts() above.
The time required to execute 2. is not the same on those two instances
executing in different VCPUS (cache misses, interrupts...).
If the TSC value that is used by the host to interpolate when
calculating the monotonic time is the same value used to calculate
the tsc_timestamp value stored in the pvclock data structure, and
a single <system_timestamp, tsc_timestamp> tuple is visible to all
vcpus simultaneously, this problem disappears. See comment on top
of pvclock_update_vm_gtod_copy for details.
Monotonicity is then guaranteed by synchronicity of the host TSCs
and guest TSCs.
Set TSC stable pvclock flag in that case, allowing the guest to read
clock from userspace.
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Diffstat (limited to 'arch/x86/kvm/svm.c')
0 files changed, 0 insertions, 0 deletions