From: "Eugenio Pérez" <eperezma@redhat.com>
To: "Michael S . Tsirkin " <mst@redhat.com>
Cc: "Stefano Garzarella" <sgarzare@redhat.com>,
jasowang@redhat.com, "Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
linux-kernel@vger.kernel.org,
"Maxime Coquelin" <mcoqueli@redhat.com>,
"Yongji Xie" <xieyongji@bytedance.com>,
"Cindy Lu" <lulu@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
virtualization@lists.linux.dev,
"Eugenio Pérez" <eperezma@redhat.com>
Subject: [PATCH v2 7/7] vduse: bump version number
Date: Tue, 16 Sep 2025 15:08:33 +0200 [thread overview]
Message-ID: <20250916130833.329087-8-eperezma@redhat.com> (raw)
In-Reply-To: <20250916130833.329087-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.
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 06b7790380b7..07ef309ed7f7 100644
--- a/drivers/vdpa/vdpa_user/vduse_dev.c
+++ b/drivers/vdpa/vdpa_user/vduse_dev.c
@@ -2121,7 +2121,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;
@@ -2188,7 +2188,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
prev parent reply other threads:[~2025-09-16 13:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 13:08 [PATCH v2 0/7] Add multiple address spaces support to VDUSE Eugenio Pérez
2025-09-16 13:08 ` [PATCH v2 1/7] vduse: add v1 API definition Eugenio Pérez
2025-09-16 13:08 ` [PATCH v2 2/7] vduse: make domain_lock an rwlock Eugenio Pérez
2025-09-17 8:36 ` Jason Wang
2025-09-17 10:01 ` Yongji Xie
2025-09-16 13:08 ` [PATCH v2 3/7] vduse: add vq group support Eugenio Pérez
2025-09-17 8:36 ` Jason Wang
2025-09-17 15:41 ` Eugenio Perez Martin
2025-09-18 6:00 ` Jason Wang
2025-09-18 6:46 ` Eugenio Perez Martin
2025-09-16 13:08 ` [PATCH v2 4/7] vduse: return internal vq group struct as map token Eugenio Pérez
2025-09-17 8:36 ` Jason Wang
2025-09-17 16:16 ` Eugenio Perez Martin
2025-09-18 6:01 ` Jason Wang
2025-09-16 13:08 ` [PATCH v2 5/7] vduse: create vduse_as to make it an array Eugenio Pérez
2025-09-17 8:46 ` Jason Wang
2025-09-17 16:34 ` Eugenio Perez Martin
2025-09-18 6:04 ` Jason Wang
2025-09-16 13:08 ` [PATCH v2 6/7] vduse: add vq group asid support Eugenio Pérez
2025-09-17 8:56 ` Jason Wang
2025-09-17 16:40 ` Eugenio Perez Martin
2025-09-18 6:07 ` Jason Wang
2025-09-18 6:57 ` Eugenio Perez Martin
2025-09-19 2:15 ` Jason Wang
2025-09-18 11:21 ` Eugenio Perez Martin
2025-09-19 2:14 ` Jason Wang
2025-09-16 13:08 ` 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=20250916130833.329087-8-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