On 5/24/22 20:30, Emanuele Giuseppe Esposito wrote:
It seems that aio_wait_kick always required a memory barrier
or atomic operation in the caller, but nobody actually
took care of doing it.

Let's put the barrier in the function instead, and pair it
with another one in AIO_WAIT_WHILE. Read aio_wait_kick()
comment for further explanation.

Suggested-by: Paolo Bonzini<[email protected]>
Signed-off-by: Emanuele Giuseppe Esposito<[email protected]>

Thanks!

Reviewed-by: Vladimir Sementsov-Ogievskiy <[email protected]>

--
Best regards,
Vladimir

Reply via email to