On 21/09/2015 09:40, Peter Lieven wrote:
My backport (Linux only and without tests etc.) of the original fix
is here:
https://github.com/plieven/qemu/commit/0ddcdc62a85f705017df16421d769e82b70f9b37
Could you be missing edec47c?
Indeed this one fixed the deadlock with -S in cmdline.
Are there other important fixes from the series?
I currently have these two:
main-loop: fix qemu_notify_event for aio_notify optimization
AioContext: fix broken ctx->dispatching optimization
The full list is
e4efd8a488d0a68b0af34d8ee245463df7c8bdf4 qemu-timer: initialize
"timers_done_ev" to set
12d69ac03b45156356b240424623719f15d8143e tests: remove irrelevant assertions
from test-aio
6493c975af75be5b8d9ade954239bdf5492b7911 aio-win32: reorganize polling loop
eabc977973103527bbb8fed69c91cfaa6691f8ab AioContext: fix broken
ctx->dispatching optimization
21a03d17f2edb1e63f7137d97ba355cc6f19d79f AioContext: fix broken placement of
event_notifier_test_and_clear
05e514b1d4d5bd4209e2c8bbc76ff05c85a235f3 AioContext: optimize clearing the
EventNotifier
edec47cfef96209987cb7922286cb384916aae02 main-loop: fix qemu_notify_event for
aio_notify optimization
fed105e2756dde98efa5e80baca02ae516dd1e51 virtio-blk-dataplane: delete bottom
half before the AioContext is freed
a076972a4d36381d610a854f0c336507650a1d34 AioContext: avoid leaking BHs on
cleanup
ca96ac44dcd290566090b2435bc828fded356ad9 AioContext: force event loop iteration
using BH
Paolo