[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [PATCH 0/5] virtio: fix some issues of "started" and "start
From: |
elohimes |
Subject: |
[Qemu-devel] [PATCH 0/5] virtio: fix some issues of "started" and "start_on_kick" flag |
Date: |
Wed, 29 May 2019 15:09:50 +0800 |
From: Xie Yongji <address@hidden>
We introduced two flags "started" and "start_on_kick" to indicate virtio
device's state before. But there still are some problems with them. So
we try to fixup them in this patchset.
The patch 1 fixes a regression bug that old guest is not able to boot with
vhost-user-blk device.
The patch 2,3,4 fix some problems with "started" and "start_on_kick" flag.
The patch 5 introduces a "use-started" property to avoid a migration
issue under Greg Kurz's suggestion [1].
[1] https://lists.gnu.org/archive/html/qemu-devel/2019-05/msg06247.html
Xie Yongji (5):
virtio: Set "start_on_kick" on virtio_set_features()
virtio: Migrate the "start_on_kick" flag
virtio: Make sure we get correct state of device on
handle_aio_output()
virtio: Don't change "started" flag on virtio_vmstate_change()
virtio: add "use-started" property
hw/block/vhost-user-blk.c | 8 +++--
hw/core/machine.c | 4 ++-
hw/virtio/virtio.c | 67 +++++++++++++++++++++++++++-----------
include/hw/virtio/virtio.h | 10 ++++++
4 files changed, 67 insertions(+), 22 deletions(-)
--
2.17.1
- [Qemu-devel] [PATCH 0/5] virtio: fix some issues of "started" and "start_on_kick" flag,
elohimes <=
- [Qemu-devel] [PATCH 1/5] virtio: Set "start_on_kick" on virtio_set_features(), elohimes, 2019/05/29
- [Qemu-devel] [PATCH 2/5] virtio: Migrate the "start_on_kick" flag, elohimes, 2019/05/29
- [Qemu-devel] [PATCH 3/5] virtio: Make sure we get correct state of device on handle_aio_output(), elohimes, 2019/05/29
- [Qemu-devel] [PATCH 4/5] virtio: Don't change "started" flag on virtio_vmstate_change(), elohimes, 2019/05/29
- [Qemu-devel] [PATCH 5/5] virtio: add "use-started" property, elohimes, 2019/05/29