aboutsummaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorAlexander Graf <agraf@suse.de>2014-05-16 17:15:21 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2014-05-21 12:01:45 +0200
commita096b3a6732f846ec57dc28b47ee9435aa0609bf (patch)
tree7fc6ccc23e0d1ea9f13e17ef706d8233f4027d3e /scripts
parent1a381811b495651ddfc2b50d7c8cfaaf375816b0 (diff)
kvmclock: Ensure time in migration never goes backward
When we migrate we ask the kernel about its current belief on what the guest time would be. However, I've seen cases where the kvmclock guest structure indicates a time more recent than the kvm returned time. To make sure we never go backwards, calculate what the guest would have seen as time at the point of migration and use that value instead of the kernel returned one when it's more recent. This bases the view of the kvmclock after migration on the same foundation in host as well as guest. Signed-off-by: Alexander Graf <agraf@suse.de> Cc: qemu-stable@nongnu.org Reviewed-by: Marcelo Tosatti <mtosatti@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions