Home
last modified time | relevance | path

Searched hist:bb6756895459f181e2f25e877d3d7a10c297b5c8 (Results 1 – 2 of 2) sorted by relevance

/qemu/tests/unit/
H A Dtest-bdrv-drain.cbb6756895459f181e2f25e877d3d7a10c297b5c8 Sat Dec 09 23:11:13 UTC 2017 Kevin Wolf <kwolf@redhat.com> test-bdrv-drain: bdrv_drain() works with cross-AioContext events

As long as nobody keeps the other I/O thread from working, there is no
reason why bdrv_drain() wouldn't work with cross-AioContext events. The
key is that the root request we're waiting for is in the AioContext
we're polling (which it always is for bdrv_drain()) so that aio_poll()
is woken up in the end.

Add a test case that shows that it works. Remove the comment in
bdrv_drain() that claims otherwise.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
/qemu/block/
H A Dio.cbb6756895459f181e2f25e877d3d7a10c297b5c8 Sat Dec 09 23:11:13 UTC 2017 Kevin Wolf <kwolf@redhat.com> test-bdrv-drain: bdrv_drain() works with cross-AioContext events

As long as nobody keeps the other I/O thread from working, there is no
reason why bdrv_drain() wouldn't work with cross-AioContext events. The
key is that the root request we're waiting for is in the AioContext
we're polling (which it always is for bdrv_drain()) so that aio_poll()
is woken up in the end.

Add a test case that shows that it works. Remove the comment in
bdrv_drain() that claims otherwise.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>