Lines Matching refs:AioContext
48 IOThread is dealing explicitly with the event loop object, AioContext
50 implicitly uses the main loop's AioContext. Code that supports running
51 in IOThreads must be aware of its AioContext.
53 AioContext supports the following services:
59 There are several old APIs that use the main loop AioContext:
71 Instead, use the AioContext functions directly (see include/block/aio.h):
84 The AioContext can be obtained from the IOThread using
86 Code that takes an AioContext argument works both in IOThreads or the main
87 loop, depending on which AioContext instance the caller passes in.
94 AioContext functions like aio_set_fd_handler(), aio_set_event_notifier(),
104 AioContext and the block layer
106 The AioContext originates from the QEMU block layer, even though nowadays
107 AioContext is a generic event loop that can be used by any QEMU subsystem.
109 The block layer has support for AioContext integrated. Each BlockDriverState
110 is associated with an AioContext using bdrv_try_change_aio_context() and
112 right AioContext. Other subsystems may wish to follow a similar approach.
126 the BlockDriverState's AioContext. The functions
130 BlockDriverState to a different AioContext.