Am 24.05.2022 um 19:30 hat Emanuele Giuseppe Esposito geschrieben: > 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 <pbonz...@redhat.com> > Signed-off-by: Emanuele Giuseppe Esposito <eespo...@redhat.com>
Thanks, applied to the block branch. Kevin
