linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: "Eugenio Pérez" <eperezma@redhat.com>
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
	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>,
	 Maxime Coquelin <mcoqueli@redhat.com>
Subject: Re: [RFC v2 6/7] vduse: send update_iotlb_v2 message
Date: Mon, 11 Aug 2025 11:24:05 +0800	[thread overview]
Message-ID: <CACGkMEsMi6Axcm_3Uin76mosPjsrwZv2qDvejoK_vLu1c3z6-Q@mail.gmail.com> (raw)
In-Reply-To: <20250807115752.1663383-7-eperezma@redhat.com>

On Thu, Aug 7, 2025 at 7:58 PM Eugenio Pérez <eperezma@redhat.com> wrote:
>
> This message lets the kernel notify userspace VDUSE backends about
> updated IOTLB mappings for a specific ASID.
>
> Signed-off-by: Eugenio Pérez <eperezma@redhat.com>

I guess this could be squashed to the previous patch for logic completeness.

Thanks


> ---
>  drivers/vdpa/vdpa_user/vduse_dev.c | 14 ++++++++++----
>  include/uapi/linux/vduse.h         |  7 +++++++
>  2 files changed, 17 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/vdpa/vdpa_user/vduse_dev.c b/drivers/vdpa/vdpa_user/vduse_dev.c
> index 145147c49930..ac7897068222 100644
> --- a/drivers/vdpa/vdpa_user/vduse_dev.c
> +++ b/drivers/vdpa/vdpa_user/vduse_dev.c
> @@ -326,7 +326,7 @@ static int vduse_dev_set_status(struct vduse_dev *dev, u8 status)
>         return vduse_dev_msg_sync(dev, &msg);
>  }
>
> -static int vduse_dev_update_iotlb(struct vduse_dev *dev,
> +static int vduse_dev_update_iotlb(struct vduse_dev *dev, u32 asid,
>                                   u64 start, u64 last)
>  {
>         struct vduse_dev_msg msg = { 0 };
> @@ -335,8 +335,14 @@ static int vduse_dev_update_iotlb(struct vduse_dev *dev,
>                 return -EINVAL;
>
>         msg.req.type = VDUSE_UPDATE_IOTLB;
> -       msg.req.iova.start = start;
> -       msg.req.iova.last = last;
> +       if (dev->api_version < VDUSE_API_VERSION_1) {
> +               msg.req.iova.start = start;
> +               msg.req.iova.last = last;
> +       } else {
> +               msg.req.iova_v2.start = start;
> +               msg.req.iova_v2.last = last;
> +               msg.req.iova_v2.asid = asid;
> +       }
>
>         return vduse_dev_msg_sync(dev, &msg);
>  }
> @@ -882,7 +888,7 @@ static int vduse_vdpa_set_map(struct vdpa_device *vdpa,
>         if (ret)
>                 return ret;
>
> -       ret = vduse_dev_update_iotlb(dev, 0ULL, ULLONG_MAX);
> +       ret = vduse_dev_update_iotlb(dev, asid, 0ULL, ULLONG_MAX);
>         if (ret) {
>                 vduse_domain_clear_map(dev->domain[asid], iotlb);
>                 return ret;
> diff --git a/include/uapi/linux/vduse.h b/include/uapi/linux/vduse.h
> index d300fd5f867f..a5f7a5edb8e0 100644
> --- a/include/uapi/linux/vduse.h
> +++ b/include/uapi/linux/vduse.h
> @@ -349,6 +349,12 @@ struct vduse_iova_range {
>         __u64 last;
>  };
>
> +struct vduse_iova_range_v2 {
> +       __u64 start;
> +       __u64 last;
> +       __u32 asid;
> +};
> +
>  /**
>   * struct vduse_dev_request - control request
>   * @type: request type
> @@ -369,6 +375,7 @@ struct vduse_dev_request {
>                 struct vduse_vq_state vq_state;
>                 struct vduse_dev_status s;
>                 struct vduse_iova_range iova;
> +               struct vduse_iova_range_v2 iova_v2;
>                 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;
> --
> 2.50.1
>


  reply	other threads:[~2025-08-11  3:24 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
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 [this message]
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=CACGkMEsMi6Axcm_3Uin76mosPjsrwZv2qDvejoK_vLu1c3z6-Q@mail.gmail.com \
    --to=jasowang@redhat.com \
    --cc=eperezma@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;
as well as URLs for NNTP newsgroup(s).