diff options
| author | Kevin Wolf | 2017-12-10 00:11:13 +0100 |
|---|---|---|
| committer | Kevin Wolf | 2018-06-18 15:03:25 +0200 |
| commit | bb6756895459f181e2f25e877d3d7a10c297b5c8 (patch) | |
| tree | b053dbf25158a20a81743e720480164001d77006 /linux-user/cpu_loop-common.h | |
| parent | Merge remote-tracking branch 'remotes/dgilbert/tags/pull-migration-20180615a'... (diff) | |
| download | qemu-bb6756895459f181e2f25e877d3d7a10c297b5c8.tar.gz qemu-bb6756895459f181e2f25e877d3d7a10c297b5c8.tar.xz qemu-bb6756895459f181e2f25e877d3d7a10c297b5c8.zip | |
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>
Diffstat (limited to 'linux-user/cpu_loop-common.h')
0 files changed, 0 insertions, 0 deletions