From 12a195fa343aae2ead1301ce04727bd0ae25eb15 Mon Sep 17 00:00:00 2001 From: Eugenio Pérez Date: Mon, 14 Mar 2022 18:34:54 +0100 Subject: vdpa: Expose VHOST_F_LOG_ALL on SVQ SVQ is able to log the dirty bits by itself, so let's use it to not block migration. Also, ignore set and clear of VHOST_F_LOG_ALL on set_features if SVQ is enabled. Even if the device supports it, the reports would be nonsense because SVQ memory is in the qemu region. The log region is still allocated. Future changes might skip that, but this series is already long enough. Signed-off-by: Eugenio Pérez Acked-by: Michael S. Tsirkin Signed-off-by: Jason Wang --- include/hw/virtio/vhost-vdpa.h | 1 + 1 file changed, 1 insertion(+) (limited to 'include/hw/virtio') diff --git a/include/hw/virtio/vhost-vdpa.h b/include/hw/virtio/vhost-vdpa.h index ee8e939ad0..a29dbb3f53 100644 --- a/include/hw/virtio/vhost-vdpa.h +++ b/include/hw/virtio/vhost-vdpa.h @@ -30,6 +30,7 @@ typedef struct vhost_vdpa { bool iotlb_batch_begin_sent; MemoryListener listener; struct vhost_vdpa_iova_range iova_range; + uint64_t acked_features; bool shadow_vqs_enabled; /* IOVA mapping used by the Shadow Virtqueue */ VhostIOVATree *iova_tree; -- cgit v1.2.3-55-g7522