From edec47cfef96209987cb7922286cb384916aae02 Mon Sep 17 00:00:00 2001 From: Paolo Bonzini Date: Fri, 24 Jul 2015 13:42:55 +0200 Subject: [PATCH] main-loop: fix qemu_notify_event for aio_notify optimization aio_notify can be optimized away, and in fact almost always will. However, qemu_notify_event is used in places where this is incorrect---most notably, when handling SIGTERM. When aio_notify is optimized away, it is possible that QEMU enters a blocking ppoll immediately afterwards and stays there, without reaching main_loop_should_exit(). Fix this by using a bottom half. The bottom half can be optimized too, but scheduling it is enough for the ppoll not to block. The hang is thus avoided. Reported-by: Peter Maydell Signed-off-by: Paolo Bonzini Reviewed-by: Stefan Hajnoczi Message-id: 1437738175-23624-1-git-send-email-pbonzini@redhat.com Signed-off-by: Peter Maydell --- main-loop.c | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/main-loop.c b/main-loop.c index 82875a4dfd..39970437f8 100644 --- a/main-loop.c +++ b/main-loop.c @@ -114,6 +114,14 @@ static int qemu_signal_init(void) #endif static AioContext *qemu_aio_context; +static QEMUBH *qemu_notify_bh; + +static void notify_event_cb(void *opaque) +{ + /* No need to do anything; this bottom half is only used to + * kick the kernel out of ppoll/poll/WaitForMultipleObjects. + */ +} AioContext *qemu_get_aio_context(void) { @@ -125,7 +133,7 @@ void qemu_notify_event(void) if (!qemu_aio_context) { return; } - aio_notify(qemu_aio_context); + qemu_bh_schedule(qemu_notify_bh); } static GArray *gpollfds; @@ -144,6 +152,7 @@ int qemu_init_main_loop(Error **errp) } qemu_aio_context = aio_context_new(&local_error); + qemu_notify_bh = qemu_bh_new(notify_event_cb, NULL); if (!qemu_aio_context) { error_propagate(errp, local_error); return -EMFILE; -- GitLab