From: "Eugenio Pérez" <eperezma@redhat.com>
To: "Michael S . Tsirkin " <mst@redhat.com>
Cc: "Maxime Coquelin" <mcoqueli@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
"Stefano Garzarella" <sgarzare@redhat.com>,
"Yongji Xie" <xieyongji@bytedance.com>,
jasowang@redhat.com, "Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Cindy Lu" <lulu@redhat.com>,
"Eugenio Pérez" <eperezma@redhat.com>
Subject: [PATCH v10 8/8] vduse: bump version number
Date: Wed, 17 Dec 2025 12:24:14 +0100 [thread overview]
Message-ID: <20251217112414.2374672-9-eperezma@redhat.com> (raw)
In-Reply-To: <20251217112414.2374672-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>
Reviewed-by: Xie Yongji <xieyongji@bytedance.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 786ab2378825..15860bd331a6 100644
--- a/drivers/vdpa/vdpa_user/vduse_dev.c
+++ b/drivers/vdpa/vdpa_user/vduse_dev.c
@@ -2163,7 +2163,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;
@@ -2230,7 +2230,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.52.0
prev parent reply other threads:[~2025-12-17 11:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 11:24 [PATCH v10 0/8] Add multiple address spaces support to VDUSE Eugenio Pérez
2025-12-17 11:24 ` [PATCH v10 1/8] vduse: add v1 API definition Eugenio Pérez
2025-12-17 11:24 ` [PATCH v10 2/8] vduse: add vq group support Eugenio Pérez
2025-12-18 6:46 ` Jason Wang
2025-12-18 10:06 ` Eugenio Perez Martin
2025-12-17 11:24 ` [PATCH v10 3/8] vduse: return internal vq group struct as map token Eugenio Pérez
2025-12-17 11:24 ` [PATCH v10 4/8] vduse: refactor vdpa_dev_add for goto err handling Eugenio Pérez
2025-12-17 11:24 ` [PATCH v10 5/8] vduse: remove unused vaddr parameter of vduse_domain_free_coherent Eugenio Pérez
2025-12-17 11:24 ` [PATCH v10 6/8] vduse: take out allocations from vduse_dev_alloc_coherent Eugenio Pérez
2025-12-18 5:45 ` Jason Wang
2025-12-18 8:40 ` Eugenio Perez Martin
2025-12-17 11:24 ` [PATCH v10 7/8] vduse: add vq group asid support Eugenio Pérez
2025-12-18 6:44 ` Jason Wang
2025-12-18 13:10 ` Eugenio Perez Martin
2025-12-23 1:11 ` Jason Wang
2025-12-23 13:15 ` Eugenio Perez Martin
2025-12-24 0:20 ` Jason Wang
2025-12-24 7:38 ` Eugenio Perez Martin
2025-12-25 2:23 ` Jason Wang
2025-12-26 11:38 ` Eugenio Perez Martin
2025-12-29 2:56 ` Jason Wang
2025-12-17 11:24 ` 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=20251217112414.2374672-9-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®