From: "Eugenio Pérez" <eperezma@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, chenbox@nvidia.com,
Yongji Xie <xieyongji@bytedance.com>,
mst@redhat.com, jasowangio@gmail.com, david.marchand@redhat.com
Subject: [PATCH 9/9] vhost: Support vduse suspend feature
Date: Thu, 24 Sep 2026 12:15:04 +0200 [thread overview]
Message-ID: <20260924101504.810315-10-eperezma@redhat.com> (raw)
In-Reply-To: <20260924101504.810315-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 8f45e905b4b4..99d7102425ff 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 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
prev parent reply other threads:[~2026-09-24 10:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 10:14 [PATCH 0/9] Add vduse live migration features Eugenio Pérez
2026-09-24 10:14 ` [PATCH 1/9] uapi: import VDUSE and VFIO header from v7.3-rc3 kernel Eugenio Pérez
2026-09-24 12:32 ` Eugenio Perez Martin
2026-09-24 14:00 ` David Marchand
2026-09-24 15:37 ` Stephen Hemminger
2026-09-25 10:21 ` Eugenio Perez Martin
2026-09-24 15:38 ` Stephen Hemminger
2026-09-24 15:50 ` Maxime Coquelin
2026-09-25 9:56 ` Eugenio Perez Martin
2026-09-24 10:14 ` [PATCH 2/9] vhost: introduce ASID support Eugenio Pérez
2026-09-24 10:14 ` [PATCH 3/9] vhost: add VDUSE API version negotiation Eugenio Pérez
2026-09-24 10:14 ` [PATCH 4/9] vhost: add virtqueues groups support to VDUSE Eugenio Pérez
2026-09-24 10:15 ` [PATCH 5/9] vhost: add ASID support to VDUSE IOTLB operations Eugenio Pérez
2026-09-24 10:15 ` [PATCH 6/9] vhost: claim VDUSE support for API version 1 Eugenio Pérez
2026-09-24 10:15 ` [PATCH 7/9] vhost: add net status feature to VDUSE Eugenio Pérez
2026-09-24 10:15 ` [PATCH 8/9] vhost: Support VDUSE QUEUE_READY feature Eugenio Pérez
2026-09-24 10:15 ` Eugenio Pérez [this message]
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=20260924101504.810315-10-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.