-
Stefan Hajnoczi authored
There is no need for the AioContext lock in aio_wait_bh_oneshot(). It's easy to remove the lock from existing callers and then switch from AIO_WAIT_WHILE() to AIO_WAIT_WHILE_UNLOCKED() in aio_wait_bh_oneshot(). Document that the AioContext lock should not be held across aio_wait_bh_oneshot(). Holding a lock across aio_poll() can cause deadlock so we don't want callers to do that. This is a step towards getting rid of the AioContext lock. Cc: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by:
Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20230404153307.458883-1-stefanha@redhat.com>
Reviewed-by:
Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by:
Emanuele Giuseppe Esposito <eesposit@redhat.com>
Reviewed-by:
Kevin Wolf <kwolf@redhat.com>
Signed-off-by:
Kevin Wolf <kwolf@redhat.com>Stefan Hajnoczi authoredThere is no need for the AioContext lock in aio_wait_bh_oneshot(). It's easy to remove the lock from existing callers and then switch from AIO_WAIT_WHILE() to AIO_WAIT_WHILE_UNLOCKED() in aio_wait_bh_oneshot(). Document that the AioContext lock should not be held across aio_wait_bh_oneshot(). Holding a lock across aio_poll() can cause deadlock so we don't want callers to do that. This is a step towards getting rid of the AioContext lock. Cc: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by:
Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20230404153307.458883-1-stefanha@redhat.com>
Reviewed-by:
Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by:
Emanuele Giuseppe Esposito <eesposit@redhat.com>
Reviewed-by:
Kevin Wolf <kwolf@redhat.com>
Signed-off-by:
Kevin Wolf <kwolf@redhat.com>
Loading