KVM: x86: limit difference between kvmclock updates

Browse source

kvmclock updates which are isolated to a given vcpu, such as vcpu->cpu
migration, should not allow system_timestamp from the rest of the vcpus
to remain static. Otherwise ntp frequency correction applies to one
vcpu's system_timestamp but not the others.

So in those cases, request a kvmclock update for all vcpus. The worst
case for a remote vcpu to update its kvmclock is then bounded by maximum
nohz sleep latency.

Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Signed-off-by: Gleb Natapov <gleb@redhat.com>

...

This commit is contained in:

Marcelo Tosatti 2013-05-09 20:21:41 -03:00 • committed by Gleb Natapov

parent f1ed0450a5

commit 0061d53daf

2 changed files with 29 additions and 2 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

30

arch/x86/kvm/x86.c

View file

1

include/linux/kvm_host.h

View file