diff options
| author | Marcelo Tosatti <mtosatti@redhat.com> | 2013-05-09 20:21:41 -0300 |
|---|---|---|
| committer | Gleb Natapov <gleb@redhat.com> | 2013-05-15 20:36:09 +0300 |
| commit | 0061d53daf26ff713ab43ab84ae5c44b5edbefa9 (patch) | |
| tree | c9b86974498fb39210c355171c01afbae513bb59 /virt | |
| parent | f1ed0450a5fac7067590317cbf027f566b6ccbca (diff) | |
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 <mtosatti@redhat.com>
Signed-off-by: Gleb Natapov <gleb@redhat.com>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions