mirror of
https://github.com/Motorhead1991/qemu.git
synced 2025-12-11 16:00:50 -07:00
block: drop aio functions that operate on the main AioContext
The main AioContext should be accessed explicitly via qemu_get_aio_context(). Most of the time, using it is not the right thing to do. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
This commit is contained in:
parent
b47ec2c456
commit
87f68d3182
7 changed files with 12 additions and 46 deletions
|
|
@ -125,7 +125,7 @@ static bool aio_dispatch(AioContext *ctx)
|
|||
bool progress = false;
|
||||
|
||||
/*
|
||||
* We have to walk very carefully in case qemu_aio_set_fd_handler is
|
||||
* We have to walk very carefully in case aio_set_fd_handler is
|
||||
* called while we're walking.
|
||||
*/
|
||||
node = QLIST_FIRST(&ctx->aio_handlers);
|
||||
|
|
@ -183,7 +183,7 @@ bool aio_poll(AioContext *ctx, bool blocking)
|
|||
/*
|
||||
* If there are callbacks left that have been queued, we need to call them.
|
||||
* Do not call select in this case, because it is possible that the caller
|
||||
* does not need a complete flush (as is the case for qemu_aio_wait loops).
|
||||
* does not need a complete flush (as is the case for aio_poll loops).
|
||||
*/
|
||||
if (aio_bh_poll(ctx)) {
|
||||
blocking = false;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue