From: "Eugenio Pérez" <eperezma@redhat.com>
To: "Michael S . Tsirkin " <mst@redhat.com>
Cc: "Yongji Xie" <xieyongji@bytedance.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Maxime Coquelin" <mcoqueli@redhat.com>,
virtualization@lists.linux.dev,
"Stefano Garzarella" <sgarzare@redhat.com>,
jasowang@redhat.com, "Cindy Lu" <lulu@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v8 6/6] vduse: bump version number
Date: Thu, 30 Oct 2025 11:00:25 +0100 [thread overview]
Message-ID: <20251030100025.95113-7-eperezma@redhat.com> (raw)
In-Reply-To: <20251030100025.95113-1-eperezma@redhat.com>
Finalize the series by advertising VDUSE API v1 support to userspace.
Now that all required infrastructure for v1 (ASIDs, VQ groups,
update_iotlb_v2) is in place, VDUSE devices can opt in to the new
features.
Acked-by: Jason Wang <jasowang@redhat.com>
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 c6909d73d06d..7977a1be5ad6 100644
--- a/drivers/vdpa/vdpa_user/vduse_dev.c
+++ b/drivers/vdpa/vdpa_user/vduse_dev.c
@@ -2166,7 +2166,7 @@ static long vduse_ioctl(struct file *file, unsigned int cmd,
break;
ret = -EINVAL;
- if (api_version > VDUSE_API_VERSION)
+ if (api_version > VDUSE_API_VERSION_1)
break;
ret = 0;
@@ -2233,7 +2233,7 @@ static int vduse_open(struct inode *inode, struct file *file)
if (!control)
return -ENOMEM;
- control->api_version = VDUSE_API_VERSION;
+ control->api_version = VDUSE_API_VERSION_1;
file->private_data = control;
return 0;
--
2.51.0
next prev parent reply other threads:[~2025-10-30 10:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 10:00 [PATCH v8 0/6] Add multiple address spaces support to VDUSE Eugenio Pérez
2025-10-30 10:00 ` [PATCH v8 1/6] vduse: add v1 API definition Eugenio Pérez
2025-10-30 12:10 ` Yongji Xie
2025-10-30 10:00 ` [PATCH v8 2/6] vduse: add vq group support Eugenio Pérez
2025-10-30 12:18 ` Yongji Xie
2025-10-30 10:00 ` [PATCH v8 3/6] vduse: return internal vq group struct as map token Eugenio Pérez
2025-10-30 10:00 ` [PATCH v8 4/6] vduse: refactor vdpa_dev_add for goto err handling Eugenio Pérez
2025-10-31 2:33 ` Yongji Xie
2025-10-30 10:00 ` [PATCH v8 5/6] vduse: add vq group asid support Eugenio Pérez
2025-10-30 11:52 ` Yongji Xie
2025-10-31 6:30 ` Eugenio Perez Martin
2025-10-31 6:51 ` [External] " Yongji Xie
2025-10-31 7:01 ` Yongji Xie
2025-10-31 14:08 ` Eugenio Perez Martin
2025-11-03 2:55 ` Yongji Xie
2025-11-03 6:40 ` Eugenio Perez Martin
2025-11-03 7:13 ` Yongji Xie
2025-11-03 8:19 ` Eugenio Perez Martin
2025-11-03 8:56 ` Yongji Xie
2025-11-03 9:26 ` Jason Wang
2025-11-03 9:45 ` Yongji Xie
2025-10-30 10:00 ` Eugenio Pérez [this message]
2025-10-31 2:33 ` [PATCH v8 6/6] vduse: bump version number Yongji Xie
2025-10-31 2:34 ` Yongji Xie
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=20251030100025.95113-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
all inboxes | Powered by JetHome®