From: "Eugenio Pérez" <eperezma@redhat.com>
To: "Michael S . Tsirkin " <mst@redhat.com>
Cc: virtualization@lists.linux.dev,
"Yongji Xie" <xieyongji@bytedance.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Maxime Coquelin" <mcoqueli@redhat.com>,
"Stefano Garzarella" <sgarzare@redhat.com>,
jasowang@redhat.com, "Eugenio Pérez" <eperezma@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Cindy Lu" <lulu@redhat.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v15 02/13] vduse: add v1 API definition
Date: Mon, 19 Jan 2026 15:32:55 +0100 [thread overview]
Message-ID: <20260119143306.1818855-3-eperezma@redhat.com> (raw)
In-Reply-To: <20260119143306.1818855-1-eperezma@redhat.com>
This allows the kernel to detect whether the userspace VDUSE device
supports the VQ group and ASID features. VDUSE devices that don't set
the V1 API will not receive the new messages, and vdpa device will be
created with only one vq group and asid.
The next patches implement the new feature incrementally, only enabling
the VDUSE device to set the V1 API version by the end of the series.
Acked-by: Jason Wang <jasowang@redhat.com>
Reviewed-by: Xie Yongji <xieyongji@bytedance.com>
Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
---
include/uapi/linux/vduse.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/include/uapi/linux/vduse.h b/include/uapi/linux/vduse.h
index 10ad71aa00d6..ccb92a1efce0 100644
--- a/include/uapi/linux/vduse.h
+++ b/include/uapi/linux/vduse.h
@@ -10,6 +10,10 @@
#define VDUSE_API_VERSION 0
+/* VQ groups and ASID support */
+
+#define VDUSE_API_VERSION_1 1
+
/*
* Get the version of VDUSE API that kernel supported (VDUSE_API_VERSION).
* This is used for future extension.
--
2.52.0
next prev parent reply other threads:[~2026-01-19 14:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 14:32 [PATCH v15 00/13] Add multiple address spaces support to VDUSE Eugenio Pérez
2026-01-19 14:32 ` [PATCH v15 01/13] vhost: move vdpa group bound check to vhost_vdpa Eugenio Pérez
2026-01-19 14:32 ` Eugenio Pérez [this message]
2026-01-19 14:32 ` [PATCH v15 03/13] vduse: add vq group support Eugenio Pérez
2026-01-19 14:32 ` [PATCH v15 04/13] vduse: return internal vq group struct as map token Eugenio Pérez
2026-01-19 14:32 ` [PATCH v15 05/13] vdpa: document set_group_asid thread safety Eugenio Pérez
2026-01-19 14:32 ` [PATCH v15 06/13] vhost: forbid change vq groups ASID if DRIVER_OK is set Eugenio Pérez
2026-01-19 14:33 ` [PATCH v15 07/13] vduse: refactor vdpa_dev_add for goto err handling Eugenio Pérez
2026-01-19 14:33 ` [PATCH v15 08/13] vduse: remove unused vaddr parameter of vduse_domain_free_coherent Eugenio Pérez
2026-01-19 14:33 ` [PATCH v15 09/13] vduse: take out allocations from vduse_dev_alloc_coherent Eugenio Pérez
2026-01-19 14:33 ` [PATCH v15 10/13] vduse: merge tree search logic of IOTLB_GET_FD and IOTLB_GET_INFO ioctls Eugenio Pérez
2026-01-19 14:33 ` [PATCH v15 11/13] vduse: add vq group asid support Eugenio Pérez
2026-01-19 14:33 ` [PATCH v15 12/13] vduse: bump version number Eugenio Pérez
2026-01-19 14:33 ` [PATCH v15 13/13] Documentation: Add documentation for VDUSE Address Space IDs 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=20260119143306.1818855-3-eperezma@redhat.com \
--to=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=lvivier@redhat.com \
--cc=mcoqueli@redhat.com \
--cc=mst@redhat.com \
--cc=sgarzare@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xieyongji@bytedance.com \
--cc=xuanzhuo@linux.alibaba.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