From: "Eugenio Pérez" <eperezma@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: mst@redhat.com, david.marchand@redhat.com, dev@dpdk.org,
Yongji Xie <xieyongji@bytedance.com>,
chenbox@nvidia.com, Bruce Richardson <bruce.richardson@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>,
jasowangio@gmail.com
Subject: [PATCH v3 9/9] vhost: Support vduse suspend feature
Date: Tue, 29 Sep 2026 12:53:39 +0200 [thread overview]
Message-ID: <20260929105339.1554051-10-eperezma@redhat.com> (raw)
In-Reply-To: <20260929105339.1554051-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 | 42 +++++++++++++++++++++++++++++++++++++++++-
lib/vhost/vhost.h | 1 +
2 files changed, 42 insertions(+), 1 deletion(-)
diff --git a/lib/vhost/vduse.c b/lib/vhost/vduse.c
index bcbd9fcd6d52..cdff4df84a84 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)
{
@@ -416,6 +417,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);
@@ -537,6 +539,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) {
@@ -567,11 +575,43 @@ 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;
+
+ ret = dev->notify_ops->vring_state_changed(dev->vid, i, false);
+ if (ret) {
+ VHOST_CONFIG_LOG(dev->ifname, ERR,
+ "Failed to disable VQ %u for suspend", i);
+ resp.result = VDUSE_REQ_RESULT_FAILED;
+ goto out;
+ }
+ }
+ dev->vduse_suspended = true;
+ resp.result = VDUSE_REQ_RESULT_OK;
+ break;
+
default:
resp.result = VDUSE_REQ_RESULT_FAILED;
break;
}
+out:
resp.request_id = req.request_id;
ret = write(dev->vduse_dev_fd, &resp, sizeof(resp));
diff --git a/lib/vhost/vhost.h b/lib/vhost/vhost.h
index 369ccf399146..d77e2003d4bd 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-09-29 10:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 10:53 [PATCH v3 0/9] Add vduse live migration features Eugenio Pérez
2026-09-29 10:53 ` [PATCH v3 1/9] uapi: import VDUSE and VFIO header from v7.3-rc5 kernel Eugenio Pérez
2026-09-29 11:41 ` Maxime Coquelin
2026-09-29 14:38 ` David Marchand
2026-09-29 10:53 ` [PATCH v3 2/9] vhost: introduce ASID support Eugenio Pérez
2026-09-29 12:08 ` Maxime Coquelin
2026-09-29 10:53 ` [PATCH v3 3/9] vhost: add VDUSE API version negotiation Eugenio Pérez
2026-09-29 12:28 ` Maxime Coquelin
2026-09-29 10:53 ` [PATCH v3 4/9] vhost: add virtqueues groups support to VDUSE Eugenio Pérez
2026-09-29 12:42 ` Maxime Coquelin
2026-09-29 10:53 ` [PATCH v3 5/9] vhost: add ASID support to VDUSE IOTLB operations Eugenio Pérez
2026-09-29 12:56 ` Maxime Coquelin
2026-09-29 10:53 ` [PATCH v3 6/9] vhost: claim VDUSE support for API version 1 Eugenio Pérez
2026-09-29 13:12 ` Maxime Coquelin
2026-09-29 10:53 ` [PATCH v3 7/9] vhost: add net status feature to VDUSE Eugenio Pérez
2026-09-29 13:27 ` Maxime Coquelin
2026-09-29 10:53 ` [PATCH v3 8/9] vhost: Support VDUSE QUEUE_READY feature Eugenio Pérez
2026-09-29 14:25 ` Maxime Coquelin
2026-09-29 10:53 ` Eugenio Pérez [this message]
2026-09-29 12:13 ` [PATCH v3 9/9] vhost: Support vduse suspend feature Maxime Coquelin
2026-10-03 9:54 ` [PATCH v3 0/9] Add vduse live migration features David Marchand
2026-10-05 8:11 ` Maxime Coquelin
2026-10-05 10:09 ` Eugenio Perez Martin
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=20260929105339.1554051-10-eperezma@redhat.com \
--to=eperezma@redhat.com \
--cc=bruce.richardson@intel.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=stephen@networkplumber.org \
--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