[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [PATCH v5 0/3] virtio-scsi: restart DMA after iothread
From: |
Stefan Hajnoczi |
Subject: |
[Qemu-devel] [PATCH v5 0/3] virtio-scsi: restart DMA after iothread |
Date: |
Thu, 20 Jun 2019 18:37:06 +0100 |
v5:
* Plumbing vm change state handlers into DeviceClass/BusClass is a rather
large bug fix. Instead I've combined the previous priorities approach with
the observation from Kevin and Paolo that we really want to order by qdev
tree depth.
The new qdev_add_vm_change_state_handler() API lets DeviceStates register
callbacks that execute in qdev tree depth order. This solves the
virtio-scsi bug since the virtio-scsi device's callback must complete before
its child scsi-disk's callback runs.
Is this a good compromise for everyone?
Stefan Hajnoczi (3):
vl: add qemu_add_vm_change_state_handler_prio()
qdev: add qdev_add_vm_change_state_handler()
virtio-scsi: restart DMA after iothread
hw/core/Makefile.objs | 1 +
include/hw/qdev-core.h | 5 +++
include/sysemu/sysemu.h | 2 +
hw/core/vm-change-state-handler.c | 61 +++++++++++++++++++++++++++++++
hw/scsi/scsi-bus.c | 4 +-
hw/virtio/virtio.c | 4 +-
vl.c | 59 ++++++++++++++++++++++++------
7 files changed, 120 insertions(+), 16 deletions(-)
create mode 100644 hw/core/vm-change-state-handler.c
--
2.21.0
- [Qemu-devel] [PATCH v5 0/3] virtio-scsi: restart DMA after iothread,
Stefan Hajnoczi <=
- [Qemu-devel] [PATCH v5 3/3] virtio-scsi: restart DMA after iothread, Stefan Hajnoczi, 2019/06/20
- [Qemu-devel] [PATCH v5 1/3] vl: add qemu_add_vm_change_state_handler_prio(), Stefan Hajnoczi, 2019/06/20
- [Qemu-devel] [PATCH v5 2/3] qdev: add qdev_add_vm_change_state_handler(), Stefan Hajnoczi, 2019/06/20
- Re: [Qemu-devel] [PATCH v5 0/3] virtio-scsi: restart DMA after iothread, Paolo Bonzini, 2019/06/20
- Re: [Qemu-devel] [PATCH v5 0/3] virtio-scsi: restart DMA after iothread, Kevin Wolf, 2019/06/27