block-coroutine-wrapper: use qemu_get_current_aio_context()
commitc12887e1b087e8f69d217ccae3dc7b1d059f3db3
authorStefan Hajnoczi <stefanha@redhat.com>
Tue, 12 Sep 2023 23:10:37 +0000 (12 19:10 -0400)
committerKevin Wolf <kwolf@redhat.com>
Thu, 21 Dec 2023 21:49:28 +0000 (21 22:49 +0100)
treef7e3a98d7b793b3a6ac9f7054922c5588476bc91
parent23c983c8f6b2fea22698f501aa6a2c03dadd81ba
block-coroutine-wrapper: use qemu_get_current_aio_context()

Use qemu_get_current_aio_context() in mixed wrappers and coroutine
wrappers so that code runs in the caller's AioContext instead of moving
to the BlockDriverState's AioContext. This change is necessary for the
multi-queue block layer where any thread can call into the block layer.

Most wrappers are IO_CODE where it's safe to use the current AioContext
nowadays. BlockDrivers and the core block layer use their own locks and
no longer depend on the AioContext lock for thread-safety.

The bdrv_create() wrapper invokes GLOBAL_STATE code. Using the current
AioContext is safe because this code is only called with the BQL held
from the main loop thread.

Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230912231037.826804-6-stefanha@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
scripts/block-coroutine-wrapper.py