Lines Matching full:loop

14 The main loop and ``IOThread``\ s
17 event loop.  The VNC server and the QMP monitor are both processed from the
18 same event loop, which monitors their file descriptors until they become
21 The default event loop is called the main loop (see ``main-loop.c``).  It is
22 possible to create additional event loop threads using
25 Side note: The main loop and ``IOThread`` are both event loops but their code is
31 ``IOThread``\ s allow the user to control the placement of work.  The main loop is a
33 several ``IOThread``\ s instead of just one main loop.  When set up correctly this
36 The main loop is also deeply associated with the BQL, which is a
37 scalability bottleneck in itself.  vCPU threads and the main loop use the BQL
41 The fact that all I/O processing is done in a single main loop and that the
42 BQL is contended by all vCPU threads and the main loop explain
54 ``IOThread`` is dealing explicitly with the event loop object, ``AioContext``
55 (see ``include/block/aio.h``).  Code that only works in the main loop
56 implicitly uses the main loop's ``AioContext``.  Code that supports running
65 There are several old APIs that use the main loop AioContext:
71  * LEGACY ``qemu_aio_wait()`` - run an event loop iteration
73 Since they implicitly work on the main loop they cannot be used in code that
83  * ``aio_poll()`` - run an event loop iteration
92 ``iothread_get_aio_context()`` or for the main loop using
94 works both in ``IOThread``\ s or the main loop, depending on which ``AioContext``
109 The main loop thread can wait synchronously for a condition using
115 ``AioContext`` is a generic event loop that can be used by any QEMU subsystem.
124 old APIs that implicitly use the main loop.  See