| commit | b4a3d965dee06d52281496bb5fd0a5cb5534b545 | |
| author | Jan Kiszka <jan.kiszka@siemens.com> | |
| Tue, 1 Feb 2011 21:15:43 +0000 (1 22:15 +0100) | ||
| committer | Marcelo Tosatti <mtosatti@redhat.com> | |
| Mon, 14 Feb 2011 14:39:44 +0000 (14 12:39 -0200) | ||
| tree | 3d1c0bb7600ea91eea18e27530c3afa2ec41bbf7 | treesnapshot (tar.gz zip) |
| parent | aa2c364b4cf2fae4d9c8acf53ee4436ed533902d | commitdiff |
Stop current VCPU on synchronous reset requests
If some I/O operation ends up calling qemu_system_reset_request in VCPU
context, we record this and inform the io-thread, but we do not
terminate the VCPU loop. This can lead to fairly unexpected behavior if
the triggering reset operation is supposed to work synchronously.
Fix this for TCG (when run in deterministic I/O mode) by setting the
VCPU on stop and issuing a cpu_exit. KVM requires some more work on its
VCPU loop.
[ ported from qemu-kvm ]
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
If some I/O operation ends up calling qemu_system_reset_request in VCPU
context, we record this and inform the io-thread, but we do not
terminate the VCPU loop. This can lead to fairly unexpected behavior if
the triggering reset operation is supposed to work synchronously.
Fix this for TCG (when run in deterministic I/O mode) by setting the
VCPU on stop and issuing a cpu_exit. KVM requires some more work on its
VCPU loop.
[ ported from qemu-kvm ]
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
| cpus.c | diffblobblamehistory | |
| cpus.h | diffblobblamehistory | |
| vl.c | diffblobblamehistory |