summaryrefslogtreecommitdiffstats
path: root/net
diff options
context:
space:
mode:
authorAndrew Jones <drjones@redhat.com>2014-02-28 12:52:54 +0100
committerPaolo Bonzini <pbonzini@redhat.com>2014-03-04 11:50:47 +0100
commit7e44e4495a398eb553ce561f29f9148f40a3448f (patch)
tree874a17c193b6be9621fbc32ba7c7ce633e316658 /net
parentccf9844e5d99c1ee9a5b8c4f1332ac5211cbce03 (diff)
downloadlinux-7e44e4495a398eb553ce561f29f9148f40a3448f.tar.bz2
x86: kvm: rate-limit global clock updates
When we update a vcpu's local clock it may pick up an NTP correction. We can't wait an indeterminate amount of time for other vcpus to pick up that correction, so commit 0061d53daf26f introduced a global clock update. However, we can't request a global clock update on every vcpu load either (which is what happens if the tsc is marked as unstable). The solution is to rate-limit the global clock updates. Marcelo calculated that we should delay the global clock updates no more than 0.1s as follows: Assume an NTP correction c is applied to one vcpu, but not the other, then in n seconds the delta of the vcpu system_timestamps will be c * n. If we assume a correction of 500ppm (worst-case), then the two vcpus will diverge 50us in 0.1s, which is a considerable amount. Signed-off-by: Andrew Jones <drjones@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions