Add sanity check to address the following concern:
During migration, all we pass the index of the request;
the rest can be re-read from the ring.
This is not generally enough if any available requests are outstanding.
Imagine a ring of size 4. Below A means available U means used.
A 1
A 2
U 2
A 2
U 2
A 2
U 2
A 2
U 2
At this point available ring has wrapped around, the only
way to know head 1 is outstanding is because backend
has stored this info somewhere.
The reason we manage to migrate without tracking this in migration
state is because we flush outstanding requests before
migration.
This flush is device-specific though, let's add
a safeguard in virtio core to ensure it's done properly.
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>
---
Changes from v1:
v1 was against the wrong tree, it didn't build against qemu.git
hw/virtio.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/virtio.c b/hw/virtio.c
index f40a8c5..6227642 100644
--- a/hw/virtio.c
+++ b/hw/virtio.c
@@ -788,6 +788,8 @@ void virtio_save(VirtIODevice *vdev, QEMUFile *f)
if (vdev->vq[i].vring.num == 0)
break;
+ assert(!vdev->vq[i].inuse);
+
qemu_put_be32(f, vdev->vq[i].vring.num);
qemu_put_be64(f, vdev->vq[i].pa);
qemu_put_be16s(f, &vdev->vq[i].last_avail_idx);
--
MST
