diff options
author | kfraser@localhost.localdomain <kfraser@localhost.localdomain> | 2007-06-20 14:36:11 +0100 |
---|---|---|
committer | kfraser@localhost.localdomain <kfraser@localhost.localdomain> | 2007-06-20 14:36:11 +0100 |
commit | d5efa0e4b7eacb505888eeea2c038b4c95b509df (patch) | |
tree | 755d5bc676d7e9c53b75c2c0487f517fbaec3c3c /tools/misc/xen-python-path | |
parent | 9b6d355987d5cb552305e595177346333f5a1746 (diff) | |
download | xen-d5efa0e4b7eacb505888eeea2c038b4c95b509df.tar.gz xen-d5efa0e4b7eacb505888eeea2c038b4c95b509df.tar.bz2 xen-d5efa0e4b7eacb505888eeea2c038b4c95b509df.zip |
hvm: Fix ioemu Qcow support.
Normally by default, SIGUSR2 is not blocked, so the signal masks of
SIGUSR2 in all threads is unblocked.
When creating HVM guest, if we use the Qcow format image file, in the
main thread, Qcow uses SIGUSR2 to be notified of the completion of the
request after it issues an AIO request; in tools/ioemu/block.c:
bdrv_read_em(), in some point between bdrv_aio_read() and
qemu_aio_wait(), Dom0 may send a SIGUSR2 to Qemu immediately to
indicate the completion of an AIO request -- since at the moment
SIGUSR2 in main thread is blocked by qemu_aio_wait_start(), the signal
may be delivered to one non-main thread, causing the signal handler of
SIGUSR2 is invoked, then the main thread hangs in
qemu_aio_wait()->syswait()...
This patch blocks SIGUSR2 at the beginning of Qemu's main(), so it
ensures SIGUSR2 is blocked by default when a new thread is created,
then only the threads that use the signal unblock it.
Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
Diffstat (limited to 'tools/misc/xen-python-path')
0 files changed, 0 insertions, 0 deletions