From: "Eugenio Pérez" <eperezma@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: Yongji Xie <xieyongji@bytedance.com>,
david.marchand@redhat.com, dev@dpdk.org, mst@redhat.com,
jasowangio@gmail.com, chenbox@nvidia.com
Subject: [RFC v4 10/11] vhost: Support vduse suspend feature
Date: Tue, 7 Jul 2026 14:45:06 +0200 [thread overview]
Message-ID: <20260707124507.251729-11-eperezma@redhat.com> (raw)
In-Reply-To: <20260707124507.251729-1-eperezma@redhat.com>
Add support for the VDUSE_F_SUSPEND feature.
The suspend feature allows the driver to stop the device from processing
the virtqueues. This ensures that the virtqueue state can be fetched
reliably in a live migration.
Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
---
lib/vhost/vduse.c | 35 ++++++++++++++++++++++++++++++++++-
lib/vhost/vhost.h | 1 +
2 files changed, 35 insertions(+), 1 deletion(-)
diff --git a/lib/vhost/vduse.c b/lib/vhost/vduse.c
index cb0bbed96012..7156ec4facd7 100644
--- a/lib/vhost/vduse.c
+++ b/lib/vhost/vduse.c
@@ -46,7 +46,8 @@ static const char * const vduse_reqs_str[] = {
(id < RTE_DIM(vduse_reqs_str) ? \
vduse_reqs_str[id] : "Unknown")
-static const uint64_t supported_vduse_features = RTE_BIT64(VDUSE_F_QUEUE_READY);
+static const uint64_t supported_vduse_features =
+ RTE_BIT64(VDUSE_F_QUEUE_READY) | RTE_BIT64(VDUSE_F_SUSPEND);
static uint64_t vduse_vq_to_group(struct virtio_net *dev, struct vhost_virtqueue *vq)
{
@@ -412,6 +413,7 @@ vduse_device_stop(struct virtio_net *dev)
vhost_destroy_device_notify(dev);
dev->flags &= ~VIRTIO_DEV_READY;
+ dev->vduse_suspended = false;
for (i = 0; i < dev->nr_vring; i++)
vduse_vring_cleanup(dev, i);
@@ -518,6 +520,12 @@ vduse_events_handler(int fd, void *arg, int *close __rte_unused)
resp.result = VDUSE_REQ_RESULT_FAILED;
break;
}
+ if (dev->vduse_suspended) {
+ VHOST_CONFIG_LOG(dev->ifname, ERR,
+ "SET_VQ_READY received on suspended device");
+ resp.result = VDUSE_REQ_RESULT_FAILED;
+ break;
+ }
i = req.vq_ready.num;
if (i >= dev->nr_vring) {
@@ -548,6 +556,31 @@ vduse_events_handler(int fd, void *arg, int *close __rte_unused)
vq->enabled = req.vq_ready.ready;
resp.result = VDUSE_REQ_RESULT_OK;
break;
+ case VDUSE_SUSPEND:
+ if (!(dev->vduse_features & RTE_BIT64(VDUSE_F_SUSPEND))) {
+ VHOST_CONFIG_LOG(dev->ifname, ERR,
+ "Unnegotiated suspend message");
+ resp.result = VDUSE_REQ_RESULT_FAILED;
+ break;
+ }
+ if (!(dev->status & VIRTIO_DEVICE_STATUS_DRIVER_OK)) {
+ VHOST_CONFIG_LOG(dev->ifname, ERR,
+ "Unexpected suspend message with no DRIVER_OK");
+ resp.result = VDUSE_REQ_RESULT_FAILED;
+ break;
+ }
+ for (i = 0; dev->notify_ops != NULL &&
+ dev->notify_ops->vring_state_changed != NULL &&
+ i < dev->nr_vring; i++) {
+ if (dev->virtqueue[i] == dev->cvq)
+ continue;
+
+ dev->notify_ops->vring_state_changed(dev->vid, i, false);
+ }
+ dev->vduse_suspended = true;
+ resp.result = VDUSE_REQ_RESULT_OK;
+ break;
+
default:
resp.result = VDUSE_REQ_RESULT_FAILED;
break;
diff --git a/lib/vhost/vhost.h b/lib/vhost/vhost.h
index c2b645c2d4b0..f0e7953e3bdc 100644
--- a/lib/vhost/vhost.h
+++ b/lib/vhost/vhost.h
@@ -534,6 +534,7 @@ struct __rte_cache_aligned virtio_net {
int vduse_dev_fd;
uint64_t vduse_api_ver;
uint64_t vduse_features;
+ bool vduse_suspended;
struct vhost_virtqueue *cvq;
--
2.55.0
next prev parent reply other threads:[~2026-07-07 12:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 12:44 [RFC v4 00/11] Add vduse live migration features Eugenio Pérez
2026-07-07 12:44 ` [RFC v4 01/11] uapi: align VDUSE header for ASID Eugenio Pérez
2026-07-07 12:44 ` [RFC v4 02/11] vhost: introduce ASID support Eugenio Pérez
2026-07-07 12:44 ` [RFC v4 03/11] vhost: add VDUSE API version negotiation Eugenio Pérez
2026-07-07 12:45 ` [RFC v4 04/11] vhost: add virtqueues groups support to VDUSE Eugenio Pérez
2026-07-07 12:45 ` [RFC v4 05/11] vhost: add ASID support to VDUSE IOTLB operations Eugenio Pérez
2026-07-07 12:45 ` [RFC v4 06/11] vhost: claim VDUSE support for API version 1 Eugenio Pérez
2026-07-07 12:45 ` [RFC v4 07/11] vhost: add net status feature to VDUSE Eugenio Pérez
2026-07-07 12:45 ` [RFC v4 08/11] uapi: Align vduse.h for enable and suspend VDUSE messages Eugenio Pérez
2026-07-07 12:45 ` [RFC v4 09/11] vhost: Support VDUSE QUEUE_READY feature Eugenio Pérez
2026-07-07 12:45 ` Eugenio Pérez [this message]
2026-07-07 12:45 ` [RFC v4 11/11] doc: add release notes for VDUSE live migration support 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=20260707124507.251729-11-eperezma@redhat.com \
--to=eperezma@redhat.com \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jasowangio@gmail.com \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=xieyongji@bytedance.com \
/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