From: "Eugenio Pérez" <eperezma@redhat.com>
To: qemu-devel@nongnu.org
Cc: Cindy Lu <lulu@redhat.com>, Shannon Nelson <snelson@pensando.io>,
longpeng2@huawei.com, virtualization@lists.linux-foundation.org,
Harpreet Singh Anand <hanand@xilinx.com>,
si-wei.liu@oracle.com, Stefan Hajnoczi <stefanha@redhat.com>,
Eli Cohen <eli@mellanox.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Gautam Dawar <gdawar@xilinx.com>,
Laurent Vivier <lvivier@redhat.com>,
Liuxiangdong <liuxiangdong5@huawei.com>,
alvaro.karsz@solid-run.com, Parav Pandit <parav@mellanox.com>,
Stefano Garzarella <sgarzare@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Zhu Lingshan <lingshan.zhu@intel.com>,
"Gonglei (Arei)" <arei.gonglei@huawei.com>,
Lei Yang <leiyang@redhat.com>
Subject: [PATCH v3 13/14] vdpa: block migration if SVQ does not admit a feature
Date: Wed, 15 Feb 2023 18:38:49 +0100 [thread overview]
Message-ID: <20230215173850.298832-14-eperezma@redhat.com> (raw)
In-Reply-To: <20230215173850.298832-1-eperezma@redhat.com>
Next patches enable devices to be migrated even if vdpa netdev has not
been started with x-svq. However, not all devices are migratable, so we
need to block migration if we detect that.
Block migration if we detect the device expose a feature SVQ does not
know how to work with.
Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
---
hw/virtio/vhost-vdpa.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/hw/virtio/vhost-vdpa.c b/hw/virtio/vhost-vdpa.c
index 3a85f9f1ed..9b8c22bda3 100644
--- a/hw/virtio/vhost-vdpa.c
+++ b/hw/virtio/vhost-vdpa.c
@@ -461,6 +461,15 @@ static int vhost_vdpa_init(struct vhost_dev *dev, void *opaque, Error **errp)
if (!(backend_features & BIT_ULL(VHOST_BACKEND_F_SUSPEND))) {
error_setg(&dev->migration_blocker,
"vhost-vdpa backend lacks VHOST_BACKEND_F_SUSPEND feature.");
+ } else {
+ /* We don't have dev->features yet */
+ uint64_t features;
+ ret = vhost_vdpa_get_dev_features(dev, &features);
+ if (unlikely(ret)) {
+ error_setg_errno(errp, -ret, "Could not get device features");
+ return ret;
+ }
+ vhost_svq_valid_features(features, &dev->migration_blocker);
}
}
--
2.31.1
next prev parent reply other threads:[~2023-02-15 17:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 17:38 [PATCH v3 00/14] Dynamically switch to vhost shadow virtqueues at vdpa net migration Eugenio Pérez
2023-02-15 17:38 ` [PATCH v3 01/14] vdpa net: move iova tree creation from init to start Eugenio Pérez
2023-02-15 17:38 ` [PATCH v3 02/14] vdpa: stop svq at vhost_vdpa_dev_start(false) Eugenio Pérez
2023-02-15 17:38 ` [PATCH v3 03/14] vdpa: Negotiate _F_SUSPEND feature Eugenio Pérez
2023-02-15 17:38 ` [PATCH v3 04/14] vdpa: add vhost_vdpa_suspend Eugenio Pérez
2023-02-16 13:47 ` Alvaro Karsz
2023-02-16 14:35 ` Eugenio Perez Martin
2023-02-15 17:38 ` [PATCH v3 05/14] vdpa: move vhost reset after get vring base Eugenio Pérez
2023-02-15 17:38 ` [PATCH v3 06/14] vdpa: rewind at get_base, not set_base Eugenio Pérez
2023-02-15 17:38 ` [PATCH v3 07/14] vdpa net: allow VHOST_F_LOG_ALL Eugenio Pérez
2023-02-15 17:38 ` [PATCH v3 08/14] vdpa: add vdpa net migration state notifier Eugenio Pérez
2023-02-15 17:38 ` [PATCH v3 09/14] vdpa: disable RAM block discard only for the first device Eugenio Pérez
2023-02-15 17:38 ` [PATCH v3 10/14] vdpa net: block migration if the device has CVQ Eugenio Pérez
2023-02-15 17:38 ` [PATCH v3 11/14] vdpa: block migration if device has unsupported features Eugenio Pérez
2023-02-15 17:38 ` [PATCH v3 12/14] vdpa: block migration if dev does not have _F_SUSPEND Eugenio Pérez
2023-02-15 17:38 ` Eugenio Pérez [this message]
2023-02-15 17:38 ` [PATCH v3 14/14] vdpa: return VHOST_F_LOG_ALL in vhost-vdpa devices Eugenio Pérez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230215173850.298832-14-eperezma@redhat.com \
--to=eperezma@redhat.com \
--cc=alvaro.karsz@solid-run.com \
--cc=arei.gonglei@huawei.com \
--cc=eli@mellanox.com \
--cc=gdawar@xilinx.com \
--cc=hanand@xilinx.com \
--cc=jasowang@redhat.com \
--cc=leiyang@redhat.com \
--cc=lingshan.zhu@intel.com \
--cc=liuxiangdong5@huawei.com \
--cc=longpeng2@huawei.com \
--cc=lulu@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=parav@mellanox.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=si-wei.liu@oracle.com \
--cc=snelson@pensando.io \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).