mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Huang, Honglei1" <Honglei1.Huang@amd.com>
To: Demi Marie Obenour <demiobenour@gmail.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,
	Dmitry Osipenko <dmitry.osipenko@collabora.com>
Subject: Re: [PATCH v2 0/7] Add virtio gpu userptr support
Date: Wed, 2 Apr 2025 09:47:40 +0800	[thread overview]
Message-ID: <a8636797-061c-4799-8017-1fee51228e8c@amd.com> (raw)
In-Reply-To: <3baabd6b-95ba-4f84-bdef-b44d6d071aba@gmail.com>

On 2025/3/30 3:56, Demi Marie Obenour wrote:
> On 3/21/25 4:00 AM, Honglei Huang wrote:
>> From: Honglei Huang <Honglei1.Huang@amd.com>
>>
>> Hello,
>>
>> This series add virtio gpu userptr support and add libhsakmt capset.
>> The userptr feature is used for let host access guest user space memory,
>> this feature is used for GPU compute use case, to enable ROCm/OpenCL native
>> context. It should be pointed out that we are not to implement SVM here,
>> this is just a buffer based userptr implementation.
>> The libhsakmt capset is used for ROCm context, libhsakmt is like the role
>> of libdrm in Mesa.
>>
>> Patches 1-2 add libhsakmt capset and userptr blob resource flag.
> 
> libhsakmt and userptr are orthogonal from each other.
> Should the libhsakmt context be a separate patch series?

I will separate libhsakmt capset patch into another patch series.

> 
>> Patches 3-5 implement basic userptr feature, in some popular bench marks,
>> it has an efficiency of about 70% compared to bare metal in OpenCL API.
>> Patch 6 adds interval tree to manage userptrs and prevent duplicate creation.
>>
>> V2: - Split add HSAKMT context and blob userptr resource to two patches.
>>      - Remove MMU notifier related patches, cause use not moveable user space
>>        memory with MMU notifier is not a good idea.
>>      - Remove HSAKMT context check when create context, let all the context
>>        support the userptr feature.
>>      - Remove MMU notifier related content in cover letter.
>>      - Add more comments  for patch 6 in cover letter.
> 
> I have not looked at the implementation, but thanks for removing the MMU
> notifier support.  Should the interval tree be added before the feature
> is exposed to userspace?  That would prevent users who are doing kernel
> bisects from temporarily exposing a buggy feature to userspace.
Ok I will add interval tree patch before introduce the feature into user 
space in next version. Really thanks for the review.



      reply	other threads:[~2025-04-02  1:47 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
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   ` Huang, Honglei1 [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=a8636797-061c-4799-8017-1fee51228e8c@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®