From: Marcelo Tosatti Date: Thu, 9 May 2013 23:21:41 +0000 (-0300) Subject: KVM: x86: limit difference between kvmclock updates X-Git-Tag: omap-for-v3.11/fixes-for-merge-window~22^2~72 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0061d53daf26ff713ab43ab84ae5c44b5edbefa9;p=pandora-kernel.git KVM: x86: limit difference between kvmclock updates 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 Signed-off-by: Gleb Natapov --- Reading git-diff-tree failed