From: "Eugenio Pérez" <eperezma@redhat.com>
To: "Michael S . Tsirkin" <mst@redhat.com>
Cc: "Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Cindy Lu" <lulu@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Stefano Garzarella" <sgarzare@redhat.com>,
linux-kernel@vger.kernel.org,
"Maxime Coquelin" <mcoqueli@redhat.com>,
"Yongji Xie" <xieyongji@bytedance.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
virtualization@lists.linux.dev
Subject: [PATCH 6/6] vduse: advertise API V2 support
Date: Wed, 28 Jan 2026 13:45:24 +0100 [thread overview]
Message-ID: <20260128124524.875271-7-eperezma@redhat.com> (raw)
In-Reply-To: <20260128124524.875271-1-eperezma@redhat.com>
Advertise VDUSE API V2 support to userspace.
With the necessary infrastructure and feature flags in place, VDUSE
devices can now opt-in to the new API and utilize the
VDUSE_F_QUEUE_READY feature.
Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
---
drivers/vdpa/vdpa_user/vduse_dev.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/vdpa/vdpa_user/vduse_dev.c b/drivers/vdpa/vdpa_user/vduse_dev.c
index 1d93b540db4d..7b5cae065f8b 100644
--- a/drivers/vdpa/vdpa_user/vduse_dev.c
+++ b/drivers/vdpa/vdpa_user/vduse_dev.c
@@ -2224,7 +2224,7 @@ static long vduse_ioctl(struct file *file, unsigned int cmd,
switch (cmd) {
case VDUSE_GET_API_VERSION:
if (control->api_version == VDUSE_API_VERSION_NOT_ASKED)
- control->api_version = VDUSE_API_VERSION_1;
+ control->api_version = VDUSE_API_VERSION_2;
ret = put_user(control->api_version, (u64 __user *)argp);
break;
case VDUSE_SET_API_VERSION: {
@@ -2235,7 +2235,7 @@ static long vduse_ioctl(struct file *file, unsigned int cmd,
break;
ret = -EINVAL;
- if (api_version > VDUSE_API_VERSION_1)
+ if (api_version > VDUSE_API_VERSION_2)
break;
ret = 0;
--
2.52.0
prev parent reply other threads:[~2026-01-28 12:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 12:45 [PATCH 0/6] Add queue ready message to VDUSE Eugenio Pérez
2026-01-28 12:45 ` [PATCH 1/6] vduse: ensure vq->ready access is smp safe Eugenio Pérez
2026-01-29 1:16 ` Jason Wang
2026-01-29 6:20 ` Eugenio Perez Martin
2026-01-30 2:18 ` Jason Wang
2026-01-30 7:56 ` Eugenio Perez Martin
2026-02-03 4:05 ` Jason Wang
2026-02-03 10:35 ` Eugenio Perez Martin
2026-02-04 2:48 ` Jason Wang
2026-02-04 8:53 ` Eugenio Perez Martin
2026-02-05 4:04 ` Jason Wang
2026-02-05 6:30 ` Eugenio Perez Martin
2026-01-28 12:45 ` [PATCH 2/6] vduse: store control device pointer Eugenio Pérez
2026-01-28 12:45 ` [PATCH 3/6] vduse: Add API v2 definition Eugenio Pérez
2026-01-29 2:00 ` Jason Wang
2026-01-29 8:07 ` Eugenio Perez Martin
2026-01-30 2:17 ` Jason Wang
2026-01-30 8:12 ` Eugenio Perez Martin
2026-01-28 12:45 ` [PATCH 4/6] vduse: add VDUSE_GET_FEATURES ioctl Eugenio Pérez
2026-01-29 2:10 ` Jason Wang
2026-01-29 8:03 ` Eugenio Perez Martin
2026-01-28 12:45 ` [PATCH 5/6] vduse: add F_QUEUE_READY feature Eugenio Pérez
2026-01-29 2:12 ` Jason Wang
2026-01-29 6:26 ` Eugenio Perez Martin
2026-01-30 2:17 ` Jason Wang
2026-01-30 8:14 ` Eugenio Perez Martin
2026-02-03 4:00 ` Jason Wang
2026-02-03 7:27 ` Eugenio Perez Martin
2026-02-04 2:44 ` Jason Wang
2026-02-04 7:34 ` Eugenio Perez Martin
2026-02-05 4:08 ` Jason Wang
2026-02-05 6:38 ` Eugenio Perez Martin
2026-01-28 12:45 ` 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=20260128124524.875271-7-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