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 4/9] vhost: add virtqueues groups support to VDUSE
Date: Tue, 29 Sep 2026 12:53:34 +0200 [thread overview]
Message-ID: <20260929105339.1554051-5-eperezma@redhat.com> (raw)
In-Reply-To: <20260929105339.1554051-1-eperezma@redhat.com>
From: Maxime Coquelin <maxime.coquelin@redhat.com>
VDUSE API version 1 introduces the notion of virtqueue
groups, which once supported, enables the support of
multiple addresses spaces.
For VDUSE networking devices, we need two groups, one for
the datapath queues, and one for the control queue.
Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
---
lib/vhost/vduse.c | 52 +++++++++++++++++++++++++++++++++++++++++++++--
1 file changed, 50 insertions(+), 2 deletions(-)
diff --git a/lib/vhost/vduse.c b/lib/vhost/vduse.c
index ceef207ad2df..8c031168bf77 100644
--- a/lib/vhost/vduse.c
+++ b/lib/vhost/vduse.c
@@ -38,12 +38,24 @@ static const char * const vduse_reqs_str[] = {
"VDUSE_GET_VQ_STATE",
"VDUSE_SET_STATUS",
"VDUSE_UPDATE_IOTLB",
+ "VDUSE_SET_VQ_GROUP_ASID",
};
#define vduse_req_id_to_str(id) \
(id < RTE_DIM(vduse_reqs_str) ? \
vduse_reqs_str[id] : "Unknown")
+static uint64_t vduse_vq_to_group(struct virtio_net *dev, struct vhost_virtqueue *vq)
+{
+ if (dev->vduse_api_ver < 1)
+ return 0;
+
+ if (vq == dev->cvq)
+ return 1;
+
+ return 0;
+}
+
static int
vduse_inject_irq(struct virtio_net *dev, struct vhost_virtqueue *vq)
{
@@ -271,6 +283,7 @@ vduse_vring_cleanup(struct virtio_net *dev, unsigned int index)
vq->size = 0;
vq->last_used_idx = 0;
vq->last_avail_idx = 0;
+ vq->asid = 0;
}
/*
@@ -410,6 +423,7 @@ vduse_events_handler(int fd, void *arg, int *close __rte_unused)
struct vduse_dev_response resp;
struct vhost_virtqueue *vq;
uint8_t old_status = dev->status;
+ uint32_t i;
int ret;
memset(&resp, 0, sizeof(resp));
@@ -450,6 +464,34 @@ vduse_events_handler(int fd, void *arg, int *close __rte_unused)
req.iova.last - req.iova.start + 1);
resp.result = VDUSE_REQ_RESULT_OK;
break;
+ case VDUSE_SET_VQ_GROUP_ASID:
+ if (dev->vduse_api_ver < 1) {
+ resp.result = VDUSE_REQ_RESULT_FAILED;
+ break;
+ }
+
+ if (req.vq_group_asid.asid >= RTE_DIM(dev->iotlb)) {
+ VHOST_CONFIG_LOG(dev->ifname, ERR,
+ "Invalid ASID %u for group %u",
+ req.vq_group_asid.asid, req.vq_group_asid.group);
+ resp.result = VDUSE_REQ_RESULT_FAILED;
+ break;
+ }
+
+ VHOST_CONFIG_LOG(dev->ifname, INFO, "\tAssigning ASID %d to group %d",
+ req.vq_group_asid.asid, req.vq_group_asid.group);
+
+ for (i = 0; i < dev->nr_vring; i++) {
+ vq = dev->virtqueue[i];
+
+ if (vduse_vq_to_group(dev, vq) == req.vq_group_asid.group) {
+ vq->asid = req.vq_group_asid.asid;
+ VHOST_CONFIG_LOG(dev->ifname, INFO, "\t\tVQ %d gets ASID %d",
+ i, req.vq_group_asid.asid);
+ }
+ }
+ resp.result = VDUSE_REQ_RESULT_OK;
+ break;
default:
resp.result = VDUSE_REQ_RESULT_FAILED;
break;
@@ -760,6 +802,10 @@ vduse_device_create(const char *path, bool compliant_ol_flags, bool extbuf, bool
dev_config->features = features;
dev_config->vq_num = total_queues;
dev_config->vq_align = rte_mem_page_size();
+ if (ver >= 1) {
+ dev_config->ngroups = 2;
+ dev_config->nas = 2;
+ }
dev_config->config_size = sizeof(struct virtio_net_config);
memcpy(dev_config->config, &vnet_config, sizeof(vnet_config));
@@ -848,11 +894,15 @@ vduse_device_create(const char *path, bool compliant_ol_flags, bool extbuf, bool
vq = dev->virtqueue[i];
vq->reconnect_log = &dev->reconnect_log->vring[i];
+ if (i == max_queue_pairs * 2)
+ dev->cvq = vq;
+
if (reconnect)
continue;
vq_cfg.index = i;
vq_cfg.max_size = 1024;
+ vq_cfg.group = vduse_vq_to_group(dev, vq);
ret = ioctl(dev->vduse_dev_fd, VDUSE_VQ_SETUP, &vq_cfg);
if (ret) {
@@ -861,8 +911,6 @@ vduse_device_create(const char *path, bool compliant_ol_flags, bool extbuf, bool
}
}
- dev->cvq = dev->virtqueue[max_queue_pairs * 2];
-
ret = fdset_add(vduse.fdset, dev->vduse_dev_fd, vduse_events_handler, NULL, dev);
if (ret) {
VHOST_CONFIG_LOG(name, ERR, "Failed to add fd %d to vduse fdset",
--
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 ` Eugenio Pérez [this message]
2026-09-29 12:42 ` [PATCH v3 4/9] vhost: add virtqueues groups support to VDUSE 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 ` [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-5-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