[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-block] [PATCH 0/4] virtio: Merge two host notifier handling paths
From: |
Fam Zheng |
Subject: |
[Qemu-block] [PATCH 0/4] virtio: Merge two host notifier handling paths |
Date: |
Fri, 24 Jun 2016 13:12:23 +0800 |
This series is based on top of Cornelia's
[PATCH 0/6] virtio: refactor host notifiers
The benifit is we don't use event_notifier_set_handler even in non-dataplane
now, which in turn makes virtio-blk and virtio-scsi follow block layer aio
context semantics. Specifically, I/O requests must come from
blk_get_aio_context(blk) events, rather than iohandler_get_aio_context(), so
that bdrv_drained_begin/end will work as expected.
Patch 4 reverts the hack (ab27c3b5e7) we added for 2.6. Lately, commit
b880481579 added another pair of bdrv_drained_begin/end so the crash cannot
happen even without ab27c3b5e7, but in order to avoid leaking requests, patch
two is still a must.
Fam Zheng (4):
virtio: Add typedef for handle_output
virtio: Always use aio path to set host handler
virtio: Drop the unused virtio_queue_set_host_notifier_fd_handler code
Revert "mirror: Workaround for unexpected iohandler events during
completion"
block/mirror.c | 9 ---------
hw/block/dataplane/virtio-blk.c | 6 +++---
hw/scsi/virtio-scsi-dataplane.c | 9 +++++----
hw/virtio/virtio-bus.c | 13 +++++++++----
hw/virtio/virtio.c | 43 ++++++++++++-----------------------------
include/hw/virtio/virtio.h | 13 ++++++-------
6 files changed, 35 insertions(+), 58 deletions(-)
--
2.8.3
- [Qemu-block] [PATCH 0/4] virtio: Merge two host notifier handling paths,
Fam Zheng <=