Searched hist:"1581 a70ddd0cd71a8520027d7136ed1e2f6bd19b" (Results 1 – 5 of 5) sorted by relevance
/openbmc/qemu/block/ |
H A D | coroutines.h | diff 1581a70ddd0cd71a8520027d7136ed1e2f6bd19b Thu Mar 03 09:16:09 CST 2022 Emanuele Giuseppe Esposito <eesposit@redhat.com> block/coroutines: I/O and "I/O or GS" API
block coroutines functions run in different aiocontext, and are not protected by the BQL. Therefore are I/O.
On the other side, generated_co_wrapper functions use BDRV_POLL_WHILE, meaning the caller can either be the main loop or a specific iothread.
Signed-off-by: Emanuele Giuseppe Esposito <eesposit@redhat.com> Message-Id: <20220303151616.325444-25-eesposit@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|
H A D | nbd.c | diff 1581a70ddd0cd71a8520027d7136ed1e2f6bd19b Thu Mar 03 09:16:09 CST 2022 Emanuele Giuseppe Esposito <eesposit@redhat.com> block/coroutines: I/O and "I/O or GS" API
block coroutines functions run in different aiocontext, and are not protected by the BQL. Therefore are I/O.
On the other side, generated_co_wrapper functions use BDRV_POLL_WHILE, meaning the caller can either be the main loop or a specific iothread.
Signed-off-by: Emanuele Giuseppe Esposito <eesposit@redhat.com> Message-Id: <20220303151616.325444-25-eesposit@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|
H A D | block-backend.c | diff 1581a70ddd0cd71a8520027d7136ed1e2f6bd19b Thu Mar 03 09:16:09 CST 2022 Emanuele Giuseppe Esposito <eesposit@redhat.com> block/coroutines: I/O and "I/O or GS" API
block coroutines functions run in different aiocontext, and are not protected by the BQL. Therefore are I/O.
On the other side, generated_co_wrapper functions use BDRV_POLL_WHILE, meaning the caller can either be the main loop or a specific iothread.
Signed-off-by: Emanuele Giuseppe Esposito <eesposit@redhat.com> Message-Id: <20220303151616.325444-25-eesposit@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|
H A D | io.c | diff 1581a70ddd0cd71a8520027d7136ed1e2f6bd19b Thu Mar 03 09:16:09 CST 2022 Emanuele Giuseppe Esposito <eesposit@redhat.com> block/coroutines: I/O and "I/O or GS" API
block coroutines functions run in different aiocontext, and are not protected by the BQL. Therefore are I/O.
On the other side, generated_co_wrapper functions use BDRV_POLL_WHILE, meaning the caller can either be the main loop or a specific iothread.
Signed-off-by: Emanuele Giuseppe Esposito <eesposit@redhat.com> Message-Id: <20220303151616.325444-25-eesposit@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|
/openbmc/qemu/ |
H A D | block.c | diff 1581a70ddd0cd71a8520027d7136ed1e2f6bd19b Thu Mar 03 09:16:09 CST 2022 Emanuele Giuseppe Esposito <eesposit@redhat.com> block/coroutines: I/O and "I/O or GS" API
block coroutines functions run in different aiocontext, and are not protected by the BQL. Therefore are I/O.
On the other side, generated_co_wrapper functions use BDRV_POLL_WHILE, meaning the caller can either be the main loop or a specific iothread.
Signed-off-by: Emanuele Giuseppe Esposito <eesposit@redhat.com> Message-Id: <20220303151616.325444-25-eesposit@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|