diff options
| author | Eugenio Pérez <eperezma@redhat.com> | 2022-07-18 14:05:45 +0200 |
|---|---|---|
| committer | Jason Wang <jasowang@redhat.com> | 2022-07-26 16:23:54 +0800 |
| commit | 2fdac348fd3d243bb964937236af3cc27ae7af2b (patch) | |
| tree | 12a2fe78e02f7833c15ac6b012b9e5d8039cea59 /hw/virtio/vhost-vsock-pci.c | |
| parent | dd0ef128669c29734a197ca9195e7ab64e20ba2c (diff) | |
| download | qemu-2fdac348fd3d243bb964937236af3cc27ae7af2b.zip qemu-2fdac348fd3d243bb964937236af3cc27ae7af2b.tar.gz qemu-2fdac348fd3d243bb964937236af3cc27ae7af2b.tar.bz2 | |
vhost: Get vring base from vq, not svq
The SVQ vring used idx usually match with the guest visible one, as long
as all the guest buffers (GPA) maps to exactly one buffer within qemu's
VA. However, as we can see in virtqueue_map_desc, a single guest buffer
could map to many buffers in SVQ vring.
Also, its also a mistake to rewind them at the source of migration.
Since VirtQueue is able to migrate the inflight descriptors, its
responsability of the destination to perform the rewind just in case it
cannot report the inflight descriptors to the device.
This makes easier to migrate between backends or to recover them in
vhost devices that support set in flight descriptors.
Fixes: 6d0b22266633 ("vdpa: Adapt vhost_vdpa_get_vring_base to SVQ")
Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
Diffstat (limited to 'hw/virtio/vhost-vsock-pci.c')
0 files changed, 0 insertions, 0 deletions