qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH] main-loop: document IOCanReadHandler


From: Philippe Mathieu-Daudé
Subject: Re: [Qemu-devel] [PATCH] main-loop: document IOCanReadHandler
Date: Sat, 2 Jun 2018 19:28:32 -0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0

On 06/02/2018 05:52 AM, Stefan Hajnoczi wrote:
> Signed-off-by: Stefan Hajnoczi <address@hidden>
> ---
>  include/qemu/main-loop.h | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/include/qemu/main-loop.h b/include/qemu/main-loop.h
> index 6b4b60bf6d..721aa2416a 100644
> --- a/include/qemu/main-loop.h
> +++ b/include/qemu/main-loop.h
> @@ -168,6 +168,20 @@ void qemu_del_wait_object(HANDLE handle, WaitObjectFunc 
> *func, void *opaque);
>  /* async I/O support */
>  
>  typedef void IOReadHandler(void *opaque, const uint8_t *buf, int size);
> +
> +/**
> + * IOCanReadHandler: Return the number of bytes that #IOReadHandler can 
> accept
> + *
> + * This function reports how many bytes #IOReadHandler is prepared to accept.
> + * #IOReadHandler may be invoked with up to this number of bytes.  If this
> + * function returns 0 then #IOReadHandler is not invoked.
> + *
> + * This function is typically called from an event loop.  If the number of
> + * bytes changes outside the event loop (e.g. because a vcpu thread drained 
> the
> + * buffer), then it is necessary to kick the event loop so that this function
> + * is called again.  aio_notify() or qemu_notify_event() can be used to kick
> + * the event loop.
> + */
>  typedef int IOCanReadHandler(void *opaque);
>  
>  /**
> 

Thanks!

Reviewed-by: Philippe Mathieu-Daudé <address@hidden>



reply via email to

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