From: "Eugenio Pérez" <eperezma@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: david.marchand@redhat.com, mst@redhat.com, chenbox@nvidia.com,
Yongji Xie <xieyongji@bytedance.com>,
jasowang@redhat.com, dev@dpdk.org
Subject: [RFC v2 08/10] uapi: Align vduse.h for enable and suspend VDUSE messages
Date: Tue, 10 Mar 2026 20:16:43 +0100 [thread overview]
Message-ID: <20260310191645.1104892-9-eperezma@redhat.com> (raw)
In-Reply-To: <20260310191645.1104892-1-eperezma@redhat.com>
From: Super User <root@wsfd-advnetlab45.anl.eng.rdu2.dc.redhat.com>
This is a prerequisite for next patches to use them.
These features are required to properly support live migration and proper
device initialization ordering.
These are not in maintainer's branch at the moment:
https://lore.kernel.org/lkml/20260310190759.1097506-1-eperezma@redhat.com
https://lore.kernel.org/lkml/20260310191019.1099757-1-eperezma@redhat.com
Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
---
v2: Align with latest headers where API_VERSION is not bumped.
---
kernel/linux/uapi/linux/vduse.h | 29 ++++++++++++++++++++++++++++-
1 file changed, 28 insertions(+), 1 deletion(-)
diff --git a/kernel/linux/uapi/linux/vduse.h b/kernel/linux/uapi/linux/vduse.h
index e19b3c0f51b5..2aa35299ba3a 100644
--- a/kernel/linux/uapi/linux/vduse.h
+++ b/kernel/linux/uapi/linux/vduse.h
@@ -14,6 +14,12 @@
#define VDUSE_API_VERSION_1 1
+/* The VDUSE instance expects a request for vq ready */
+#define VDUSE_F_QUEUE_READY 0
+
+/* The VDUSE instance expects a request for suspend */
+#define VDUSE_F_SUSPEND 1
+
/*
* Get the version of VDUSE API that kernel supported (VDUSE_API_VERSION).
* This is used for future extension.
@@ -33,6 +39,7 @@
* @vq_align: the allocation alignment of virtqueue's metadata
* @ngroups: number of vq groups that VDUSE device declares
* @nas: number of address spaces that VDUSE device declares
+ * @vduse_features: VDUSE features
* @reserved: for future use, needs to be initialized to zero
* @config_size: the size of the configuration space
* @config: the buffer of the configuration space
@@ -49,7 +56,8 @@ struct vduse_dev_config {
__u32 vq_align;
__u32 ngroups; /* if VDUSE_API_VERSION >= 1 */
__u32 nas; /* if VDUSE_API_VERSION >= 1 */
- __u32 reserved[11];
+ __u64 vduse_features; /* if VDUSE_GET_FEATURES is not EINVAL */
+ __u32 reserved[9];
__u32 config_size;
__u8 config[];
};
@@ -63,6 +71,9 @@ struct vduse_dev_config {
*/
#define VDUSE_DESTROY_DEV _IOW(VDUSE_BASE, 0x03, char[VDUSE_NAME_MAX])
+/* Get the VDUSE supported features */
+#define VDUSE_GET_FEATURES _IOR(VDUSE_BASE, 0x04, __u64)
+
/* The ioctls for VDUSE device (/dev/vduse/$NAME) */
/**
@@ -325,6 +336,8 @@ enum vduse_req_type {
VDUSE_SET_STATUS,
VDUSE_UPDATE_IOTLB,
VDUSE_SET_VQ_GROUP_ASID,
+ VDUSE_SET_VQ_READY,
+ VDUSE_SUSPEND,
};
/**
@@ -372,6 +385,15 @@ struct vduse_iova_range_v2 {
__u32 padding;
};
+/**
+ * struct vduse_vq_ready - Virtqueue ready request message
+ * @num: Virtqueue number
+ */
+struct vduse_vq_ready {
+ __u32 num;
+ __u32 ready;
+};
+
/**
* struct vduse_dev_request - control request
* @type: request type
@@ -382,6 +404,7 @@ struct vduse_iova_range_v2 {
* @iova: IOVA range for updating
* @iova_v2: IOVA range for updating if API_VERSION >= 1
* @vq_group_asid: ASID of a virtqueue group
+ * @vq_ready: Virtqueue ready request
* @padding: padding
*
* Structure used by read(2) on /dev/vduse/$NAME.
@@ -399,6 +422,10 @@ struct vduse_dev_request {
*/
struct vduse_iova_range_v2 iova_v2;
struct vduse_vq_group_asid vq_group_asid;
+
+ /* Only if VDUSE_F_QUEUE_READY is negotiated */
+ struct vduse_vq_ready vq_ready;
+
__u32 padding[32];
};
};
--
2.53.0
next prev parent reply other threads:[~2026-03-10 19:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 19:16 [RFC v2 00/10] Add vduse live migration features Eugenio Pérez
2026-03-10 19:16 ` [RFC v2 01/10] uapi: align VDUSE header for ASID Eugenio Pérez
2026-03-10 19:16 ` [RFC v2 02/10] vhost: introduce ASID support Eugenio Pérez
2026-03-10 19:16 ` [RFC v2 03/10] vhost: add VDUSE API version negotiation Eugenio Pérez
2026-03-10 19:16 ` [RFC v2 04/10] vhost: add virtqueues groups support to VDUSE Eugenio Pérez
2026-03-10 19:16 ` [RFC v2 05/10] vhost: add ASID support to VDUSE IOTLB operations Eugenio Pérez
2026-03-10 19:16 ` [RFC v2 06/10] vhost: claim VDUSE support for API version 1 Eugenio Pérez
2026-03-10 19:16 ` [RFC v2 07/10] vhost: add net status feature to VDUSE Eugenio Pérez
2026-03-10 19:16 ` Eugenio Pérez [this message]
2026-03-10 19:16 ` [RFC v2 09/10] vhost: Support VDUSE QUEUE_READY feature Eugenio Pérez
2026-03-10 19:16 ` [RFC v2 10/10] vhost: Support vduse suspend feature 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=20260310191645.1104892-9-eperezma@redhat.com \
--to=eperezma@redhat.com \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jasowang@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox