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 8/9] vhost: Support VDUSE QUEUE_READY feature
Date: Tue, 29 Sep 2026 12:53:38 +0200 [thread overview]
Message-ID: <20260929105339.1554051-9-eperezma@redhat.com> (raw)
In-Reply-To: <20260929105339.1554051-1-eperezma@redhat.com>
Add support for the VDUSE_F_QUEUE_READY feature.
In VDUSE, the dataplane is enabled only after control virtqueue so the
device is fully configured in the destination of a live migration before
the dataplane starts. This message signals the VDUSE device when the
dataplane queues should be enabled.
Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
---
lib/vhost/vduse.c | 86 +++++++++++++++++++++++++++++++++++++++++++++--
lib/vhost/vhost.h | 1 +
2 files changed, 85 insertions(+), 2 deletions(-)
diff --git a/lib/vhost/vduse.c b/lib/vhost/vduse.c
index b51776cf3ff4..bcbd9fcd6d52 100644
--- a/lib/vhost/vduse.c
+++ b/lib/vhost/vduse.c
@@ -39,12 +39,15 @@ static const char * const vduse_reqs_str[] = {
"VDUSE_SET_STATUS",
"VDUSE_UPDATE_IOTLB",
"VDUSE_SET_VQ_GROUP_ASID",
+ "VDUSE_SET_VQ_READY",
};
#define vduse_req_id_to_str(id) \
(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 uint64_t vduse_vq_to_group(struct virtio_net *dev, struct vhost_virtqueue *vq)
{
if (dev->vduse_api_ver < 1)
@@ -519,6 +522,51 @@ vduse_events_handler(int fd, void *arg, int *close __rte_unused)
}
resp.result = VDUSE_REQ_RESULT_OK;
break;
+ case VDUSE_SET_VQ_READY:
+ if (!(dev->status & VIRTIO_DEVICE_STATUS_DRIVER_OK)) {
+ /*
+ * dev->notify_ops is NULL if !S_DRIVER_OK,
+ * vduse_device_start will check the queue readiness.
+ */
+ resp.result = VDUSE_REQ_RESULT_OK;
+ break;
+ }
+ if (!(dev->vduse_features & RTE_BIT64(VDUSE_F_QUEUE_READY))) {
+ VHOST_CONFIG_LOG(dev->ifname, ERR,
+ "Unexpected ready message with no ready feature acked");
+ resp.result = VDUSE_REQ_RESULT_FAILED;
+ break;
+ }
+
+ i = req.vq_ready.num;
+ if (i >= dev->nr_vring) {
+ VHOST_CONFIG_LOG(dev->ifname, ERR,
+ "Invalid virtqueue index: %u", i);
+ resp.result = VDUSE_REQ_RESULT_FAILED;
+ break;
+ }
+
+ vq = dev->virtqueue[i];
+ if (dev->notify_ops == NULL || dev->notify_ops->vring_state_changed == NULL) {
+ VHOST_CONFIG_LOG(dev->ifname, ERR,
+ "No ops->vring_state_changed");
+ resp.result = VDUSE_REQ_RESULT_FAILED;
+ break;
+ }
+
+ ret = dev->notify_ops->vring_state_changed(dev->vid, i,
+ req.vq_ready.ready);
+ VHOST_CONFIG_LOG(dev->ifname, INFO,
+ "\t\t VQ %d gets ready %d ok %d", i,
+ req.vq_ready.ready, ret);
+ if (ret != 0) {
+ resp.result = VDUSE_REQ_RESULT_FAILED;
+ break;
+ }
+
+ vq->enabled = req.vq_ready.ready;
+ resp.result = VDUSE_REQ_RESULT_OK;
+ break;
default:
resp.result = VDUSE_REQ_RESULT_FAILED;
break;
@@ -536,7 +584,8 @@ vduse_events_handler(int fd, void *arg, int *close __rte_unused)
if ((old_status ^ dev->status) & VIRTIO_DEVICE_STATUS_DRIVER_OK) {
if (dev->status & VIRTIO_DEVICE_STATUS_DRIVER_OK) {
/* Poll virtqueues ready states before starting device */
- ret = vduse_wait_for_virtqueues_ready(dev);
+ ret = dev->vduse_features & RTE_BIT64(VDUSE_F_QUEUE_READY) ? 0
+ : vduse_wait_for_virtqueues_ready(dev);
if (ret < 0) {
VHOST_CONFIG_LOG(dev->ifname, ERR,
"Failed to wait for virtqueues ready, aborting device start");
@@ -742,6 +791,26 @@ vduse_reconnect_start_device(struct virtio_net *dev)
return ret;
}
+/* If some error occurs just continue as if the kernel exposed no features */
+static uint64_t
+vduse_device_get_vduse_features(int control_fd, const char *log_name)
+{
+ uint64_t vduse_kernel_features;
+ int ret;
+
+ ret = ioctl(control_fd, VDUSE_GET_FEATURES, &vduse_kernel_features);
+ if (ret < 0) {
+ VHOST_CONFIG_LOG(log_name, INFO,
+ "Failed to get kernel VDUSE features, assuming not supported: %d(%s)",
+ errno, strerror(errno));
+ return 0;
+ }
+
+ VHOST_CONFIG_LOG(log_name, DEBUG, "Setting vhost kernel features: %"PRIx64,
+ vduse_kernel_features & supported_vduse_features);
+ return vduse_kernel_features & supported_vduse_features;
+}
+
int
vduse_device_create(const char *path, bool compliant_ol_flags, bool extbuf, bool linearbuf)
{
@@ -750,7 +819,7 @@ vduse_device_create(const char *path, bool compliant_ol_flags, bool extbuf, bool
struct virtio_net *dev;
struct virtio_net_config vnet_config = {{ 0 }};
uint64_t ver;
- uint64_t features;
+ uint64_t features, vduse_features = 0;
const char *name = path + strlen("/dev/vduse/");
bool reconnect = false;
@@ -834,6 +903,18 @@ vduse_device_create(const char *path, bool compliant_ol_flags, bool extbuf, bool
dev_config->ngroups = 2;
dev_config->nas = 2;
}
+
+ vduse_features = vduse_device_get_vduse_features(control_fd, name);
+ if (vduse_features) {
+ ret = ioctl(control_fd, VDUSE_SET_FEATURES, &vduse_features);
+ if (ret < 0) {
+ VHOST_CONFIG_LOG(name, ERR, "Failed to set VDUSE features: %s",
+ strerror(errno));
+ free(dev_config);
+ goto out_ctrl_close;
+ }
+ }
+
dev_config->config_size = sizeof(struct virtio_net_config);
memcpy(dev_config->config, &vnet_config, sizeof(vnet_config));
@@ -884,6 +965,7 @@ vduse_device_create(const char *path, bool compliant_ol_flags, bool extbuf, bool
dev->vduse_ctrl_fd = control_fd;
dev->vduse_dev_fd = dev_fd;
dev->vduse_api_ver = ver;
+ dev->vduse_features = vduse_features;
ret = vduse_reconnect_log_map(dev, !reconnect);
if (ret < 0)
diff --git a/lib/vhost/vhost.h b/lib/vhost/vhost.h
index 36d65bc2c162..369ccf399146 100644
--- a/lib/vhost/vhost.h
+++ b/lib/vhost/vhost.h
@@ -533,6 +533,7 @@ struct __rte_cache_aligned virtio_net {
int vduse_ctrl_fd;
int vduse_dev_fd;
uint64_t vduse_api_ver;
+ uint64_t vduse_features;
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 ` Eugenio Pérez [this message]
2026-09-29 14:25 ` [PATCH v3 8/9] vhost: Support VDUSE QUEUE_READY feature Maxime Coquelin
2026-09-29 10:53 ` [PATCH v3 9/9] vhost: Support vduse suspend feature Eugenio Pérez
2026-09-29 12:13 ` 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-9-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