From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "Eugenio Pérez" <eperezma@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>
Cc: Cindy Lu <lulu@redhat.com>, Yongji Xie <xieyongji@bytedance.com>,
Stefano Garzarella <sgarzare@redhat.com>,
virtualization@lists.linux.dev,
Laurent Vivier <lvivier@redhat.com>,
linux-kernel@vger.kernel.org,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
jasowang@redhat.com, Maxime Coquelin <mcoqueli@redhat.com>
Subject: Re: [RFC v2 5/7] vduse: add vq group asid support
Date: Fri, 8 Aug 2025 09:45:09 +0200 [thread overview]
Message-ID: <edf19f09-bd54-4297-8c5e-da331c24fc4c@redhat.com> (raw)
In-Reply-To: <20250807115752.1663383-6-eperezma@redhat.com>
On 8/7/25 1:57 PM, Eugenio Pérez wrote:
> diff --git a/include/uapi/linux/vduse.h b/include/uapi/linux/vduse.h
> index b4b139dc76bb..d300fd5f867f 100644
> --- a/include/uapi/linux/vduse.h
> +++ b/include/uapi/linux/vduse.h
> @@ -47,7 +47,8 @@ struct vduse_dev_config {
> __u32 vq_num;
> __u32 vq_align;
> __u32 ngroups; /* if VDUSE_API_VERSION >= 1 */
> - __u32 reserved[12];
> + __u32 nas; /* if VDUSE_API_VERSION >= 1 */
> + __u32 reserved[11];
> __u32 config_size;
> __u8 config[];
> };
> @@ -82,6 +83,17 @@ struct vduse_iotlb_entry {
> __u8 perm;
> };
>
> +struct vduse_iotlb_entry_v2 {
> + __u64 offset;
> + __u64 start;
> + __u64 last;
> +#define VDUSE_ACCESS_RO 0x1
> +#define VDUSE_ACCESS_WO 0x2
> +#define VDUSE_ACCESS_RW 0x3
> + __u8 perm;
> + __u32 asid;
> +};
> +
> /*
> * Find the first IOVA region that overlaps with the range [start, last]
> * and return the corresponding file descriptor. Return -EINVAL means the
> @@ -172,6 +184,16 @@ struct vduse_vq_group {
> __u32 num;
> };
>
> +/**
> + * struct vduse_vq_group - virtqueue group
> + @ @group: Index of the virtqueue group
> + * @asid: Address space ID of the group
> + */
> +struct vduse_vq_group_asid {
> + __u32 group;
> + __u32 asid;
> +};
> +
> /**
> * struct vduse_vq_info - information of a virtqueue
> * @index: virtqueue index
> @@ -232,6 +254,7 @@ struct vduse_vq_eventfd {
> * @uaddr: start address of userspace memory, it must be aligned to page size
> * @iova: start of the IOVA region
> * @size: size of the IOVA region
> + * @asid: Address space ID of the IOVA region
> * @reserved: for future use, needs to be initialized to zero
> *
> * Structure used by VDUSE_IOTLB_REG_UMEM and VDUSE_IOTLB_DEREG_UMEM
> @@ -241,7 +264,8 @@ struct vduse_iova_umem {
> __u64 uaddr;
> __u64 iova;
> __u64 size;
> - __u64 reserved[3];
> + __u32 asid;
> + __u32 reserved[5];
> };
>
> /* Register userspace memory for IOVA regions */
> @@ -265,7 +289,8 @@ struct vduse_iova_info {
> __u64 last;
> #define VDUSE_IOVA_CAP_UMEM (1 << 0)
> __u64 capability;
> - __u64 reserved[3];
> + __u32 asid; /* Only if device API version >= 1 */
> + __u32 reserved[5];
> };
>
> /*
> @@ -289,6 +314,7 @@ enum vduse_req_type {
> VDUSE_UPDATE_IOTLB,
> VDUSE_GET_VQ_GROUP,
> VDUSE_GET_VRING_DESC_GROUP,
> + VDUSE_SET_VQ_GROUP_ASID,
> };
>
> /**
> @@ -344,6 +370,8 @@ struct vduse_dev_request {
> struct vduse_dev_status s;
> struct vduse_iova_range iova;
> struct vduse_vq_group vq_group; /* Only if vduse api version >= 1 */
> + /* Only if vduse api version >= 1 */
> + struct vduse_vq_group_asid vq_group_asid;
> __u32 padding[32];
I think you need to update padding size here.
> };
> };
> @@ -367,6 +395,8 @@ struct vduse_dev_response {
> union {
> struct vduse_vq_state vq_state;
> struct vduse_vq_group vq_group; /* Only if vduse api version >= 1 */
> + /* Only if vduse api version >= 1 */
> + struct vduse_vq_group_asid vq_group_asid;
> __u32 padding[32];
> };
> };
Same
Regards,
Maxime
next prev parent reply other threads:[~2025-08-08 7:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 11:57 [RFC v2 0/7] Add multiple address spaces support to VDUSE Eugenio Pérez
2025-08-07 11:57 ` [RFC v2 1/7] vduse: add v1 API definition Eugenio Pérez
2025-08-07 11:57 ` [RFC v2 2/7] vduse: add vq group support Eugenio Pérez
2025-08-08 7:46 ` Maxime Coquelin
2025-08-11 3:09 ` Jason Wang
2025-08-11 9:51 ` Eugenio Perez Martin
2025-08-12 3:01 ` Jason Wang
2025-08-13 10:11 ` Eugenio Perez Martin
2025-08-14 3:42 ` Jason Wang
2025-08-07 11:57 ` [RFC v2 3/7] vdpa: change get_vq_map_token type to void *(*cb) Eugenio Pérez
2025-08-07 11:57 ` [RFC v2 4/7] vduse: return internal vq group struct as map token Eugenio Pérez
2025-08-11 3:11 ` Jason Wang
2025-08-11 11:03 ` Eugenio Perez Martin
2025-08-12 3:02 ` Jason Wang
2025-08-07 11:57 ` [RFC v2 5/7] vduse: add vq group asid support Eugenio Pérez
2025-08-08 7:45 ` Maxime Coquelin [this message]
2025-08-10 9:45 ` Eugenio Perez Martin
2025-08-11 3:21 ` Jason Wang
2025-08-11 11:19 ` Eugenio Perez Martin
2025-08-12 3:05 ` Jason Wang
2025-08-13 11:02 ` Eugenio Perez Martin
2025-08-07 11:57 ` [RFC v2 6/7] vduse: send update_iotlb_v2 message Eugenio Pérez
2025-08-11 3:24 ` Jason Wang
2025-08-07 11:57 ` [RFC v2 7/7] vduse: bump version number Eugenio Pérez
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=edf19f09-bd54-4297-8c5e-da331c24fc4c@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=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®