[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] main-loop: fix qemu_notify_event for aio_notify

From: Peter Maydell
Subject: Re: [Qemu-devel] [PATCH] main-loop: fix qemu_notify_event for aio_notify optimization
Date: Fri, 24 Jul 2015 11:33:33 +0100

On 24 July 2015 at 11:12, Paolo Bonzini <address@hidden> wrote:
> 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
> it will cause the ppoll not to block.  The hang is thus avoided.
> Reported-by: Peter Maydell <address@hidden>
> Signed-off-by: Paolo Bonzini <address@hidden>
> ---
>  main-loop.c | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
> diff --git a/main-loop.c b/main-loop.c
> index 82875a4..9d93478 100644
> --- a/main-loop.c
> +++ b/main-loop.c
> @@ -114,6 +114,11 @@ static int qemu_signal_init(void)
>  #endif
>  static AioContext *qemu_aio_context;
> +static QEMUBH *qemu_notify_bh;
> +
> +static void notify_event_cb(void *opaque)
> +{
> +}

Could we have a comment to explain why an empty callback
is an interesting thing to run, please? I can sort of deduce
from the commit message that the purpose of this apparently
useless thing is just to provoke the main loop into leaving
ppoll() and checking whatever condition it needs to, but it
wouldn't be very clear to me just from the code...

-- PMM

reply via email to

[Prev in Thread] Current Thread [Next in Thread]