From: "Huang, Honglei1" <Honglei1.Huang@amd.com>
To: Dmitry Osipenko <dmitry.osipenko@collabora.com>,
David Airlie <airlied@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Gurchetan Singh <gurchetansingh@chromium.org>,
Chia-I Wu <olvaffe@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Simona Vetter <simona@ffwll.ch>, Rob Clark <robdclark@gmail.com>,
Huang Rui <ray.huang@amd.com>
Cc: dri-devel@lists.freedesktop.org, virtualization@lists.linux.dev,
linux-kernel@vger.kernel.org,
Demi Marie Obenour <demiobenour@gmail.com>
Subject: Re: [PATCH v2 7/7] drm/virtio: implement userptr: add interval tree
Date: Wed, 2 Apr 2025 09:53:10 +0800 [thread overview]
Message-ID: <6e796751-86f3-42e5-b0a6-3a3602d3af13@amd.com> (raw)
In-Reply-To: <810789ec-c034-4bdd-961a-f49c67336e45@collabora.com>
On 2025/3/30 19:57, Dmitry Osipenko wrote:
> If the purpose of this feature is to dedup usrptr BOs of a the single
> process/application, can this can be done in userspace?
>
> On 3/21/25 11:00, Honglei Huang wrote:
>> int virtio_gpu_userptr_create(struct virtio_gpu_device *vgdev,
>> struct drm_file *file,
>> struct virtio_gpu_object_params *params,
>> - struct virtio_gpu_object **bo_ptr)
>> + struct virtio_gpu_object **bo_ptr,
>> + struct drm_virtgpu_resource_create_blob *rc_blob)
>> {
>> + struct virtio_gpu_fpriv *vfpriv = file->driver_priv;
>> struct virtio_gpu_object_userptr *userptr;
>> int ret, si;
>> struct sg_table *sgt;
>> @@ -187,6 +290,20 @@ int virtio_gpu_userptr_create(struct virtio_gpu_device *vgdev,
>> params->size))
>> return -EFAULT;
>>
>> + mutex_lock(&vfpriv->userptrs_tree_lock);
>> +
>> + userptr = virtio_gpu_userptr_from_addr_range(
>> + vfpriv, params->userptr, params->userptr + params->size - 1UL);
>
> Is it possible that userptr address will be same for two different
> processes?
>
> What if userptr->flags mismatch?
This situation need to be considered, I will add flag check, and add
handle the situation of increasing write permissions.
>
>> + if (userptr) {
>> + *bo_ptr = &userptr->base;
>> + rc_blob->res_handle = userptr->base.hw_res_handle;
>> + rc_blob->bo_handle = userptr->bo_handle;
>
> Doesn't BO refcount need to be bumped?
Will add Bo refcount in next version.
>
>> + rc_blob->offset = virtio_gpu_userptr_get_offset(
>> + &userptr->base, rc_blob->userptr);
>> + mutex_unlock(&vfpriv->userptrs_tree_lock);
>> + return STATE_RES_EXISTS;
>
> STATE_RES_EXISTS isn't a error code
Will use the system's built-in error code, really thanks for the review.
>
next prev parent reply other threads:[~2025-04-02 1:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 8:00 [PATCH v2 0/7] *** Add virtio gpu userptr support *** Honglei Huang
2025-03-21 8:00 ` [PATCH v2 1/7] virtio-gpu api: add HSAKMT context Honglei Huang
2025-03-21 8:00 ` [PATCH v2 2/7] virtio-gpu api: add blob userptr resource Honglei Huang
2025-03-21 8:00 ` [PATCH v2 3/7] drm/virtgpu " Honglei Huang
2025-03-21 8:00 ` [PATCH v2 4/7] drm/virtio: implement userptr: probe for the feature Honglei Huang
2025-03-21 8:00 ` [PATCH v2 5/7] drm/virtio: implement userptr: add userptr obj Honglei Huang
2025-03-21 8:00 ` [PATCH v2 6/7] drm/virtio: advertise base userptr feature to userspace Honglei Huang
2025-03-21 8:00 ` [PATCH v2 7/7] drm/virtio: implement userptr: add interval tree Honglei Huang
2025-03-30 11:57 ` Dmitry Osipenko
2025-03-30 12:04 ` Dmitry Osipenko
2025-04-02 1:53 ` Huang, Honglei1 [this message]
2025-04-02 12:34 ` Dmitry Osipenko
2025-04-02 18:45 ` Demi Marie Obenour
2025-04-03 3:28 ` Huang, Honglei1
2025-04-03 16:44 ` Dmitry Osipenko
2025-03-29 19:56 ` [PATCH v2 0/7] *** Add virtio gpu userptr support *** Demi Marie Obenour
2025-04-02 1:47 ` [PATCH v2 0/7] Add virtio gpu userptr support Huang, Honglei1
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=6e796751-86f3-42e5-b0a6-3a3602d3af13@amd.com \
--to=honglei1.huang@amd.com \
--cc=airlied@redhat.com \
--cc=demiobenour@gmail.com \
--cc=dmitry.osipenko@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gurchetansingh@chromium.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=olvaffe@gmail.com \
--cc=ray.huang@amd.com \
--cc=robdclark@gmail.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux.dev \
/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®