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 <epere...@redhat.com>
---
 drivers/vdpa/vdpa_user/vduse_dev.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/vdpa/vdpa_user/vduse_dev.c 
b/drivers/vdpa/vdpa_user/vduse_dev.c
index ac7897068222..cbbbaafa79a1 100644
--- a/drivers/vdpa/vdpa_user/vduse_dev.c
+++ b/drivers/vdpa/vdpa_user/vduse_dev.c
@@ -2123,7 +2123,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;
@@ -2190,6 +2190,7 @@ static int vduse_open(struct inode *inode, struct file 
*file)
        if (!control)
                return -ENOMEM;
 
+       control->api_version = VDUSE_API_VERSION_1;
        file->private_data = control;
 
        return 0;
-- 
2.50.1


Reply via email to