aboutsummaryrefslogtreecommitdiff
path: root/cpu-exec.c
diff options
context:
space:
mode:
authorGonglei <arei.gonglei@huawei.com>2016-08-09 15:49:15 +0800
committerPaolo Bonzini <pbonzini@redhat.com>2016-08-09 22:57:36 +0200
commit3fdd0ee393e26178a4892e101e60b011bbfaa9ea (patch)
treed1de8c2062edde691f585502af9427cacaef3ad2 /cpu-exec.c
parent93bf13c6df4d6fd1a889cae890a9570eb00eb8e5 (diff)
downloadqemu-3fdd0ee393e26178a4892e101e60b011bbfaa9ea.zip
qemu-3fdd0ee393e26178a4892e101e60b011bbfaa9ea.tar.gz
qemu-3fdd0ee393e26178a4892e101e60b011bbfaa9ea.tar.bz2
timer: set vm_clock disabled default
(commit 80dcfb8532ae76343109a48f12ba8ca1c505c179) Upon migration, the code use a timer based on vm_clock for 1ns in the future from post_load to do the event send in case host_connected differs between migration source and target. However, it's not guaranteed that the apic is ready to inject irqs into the guest, and the irq line remained high, resulting in any future interrupts going unnoticed by the guest as well. That's because 1) the migration coroutine is not blocked when it get EAGAIN while reading QEMUFile. 2) The vm_clock is enabled default currently, it doesn't rely on the calling of vm_start(), that means vm_clock timers can run before VCPUs are running. So, let's set the vm_clock disabled default, keep the initial intention of design for vm_clock timers. Meanwhile, change the test-aio usecase, using QEMU_CLOCK_REALTIME instead of QEMU_CLOCK_VIRTUAL as the block code does. CC: Paolo Bonzini <pbonzini@redhat.com> CC: Dr. David Alan Gilbert <dgilbert@redhat.com> CC: qemu-stable@nongnu.org Signed-off-by: Gonglei <arei.gonglei@huawei.com> Message-Id: <1470728955-90600-1-git-send-email-arei.gonglei@huawei.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'cpu-exec.c')
0 files changed, 0 insertions, 0 deletions