From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: "Huang, Honglei1" <Honglei1.Huang@amd.com>,
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
Subject: Re: [PATCH v2 7/7] drm/virtio: implement userptr: add interval tree
Date: Thu, 3 Apr 2025 19:44:34 +0300 [thread overview]
Message-ID: <4ca36f29-9a5d-4585-8699-f4e78dc7266e@collabora.com> (raw)
In-Reply-To: <885bf81e-0aa4-4fe7-af81-a4a4485474b7@amd.com>
On 4/3/25 06:28, Huang, Honglei1 wrote:
>
> Hi Dmitry:
>
> Really sorry for missed this comment. Yes it can be done in UMD,
> actually the interval tree is used with the MMU notifier normally,
> it is for preventing create same MMU notifier for overlapped areas.
> Cause this version patch set doesn't have MMU notifier, removing
> interval tree is reasonable.
>
> Hi Demi:
> Adding interval tree can make virtio userptr has robust check, it can be
> done in UMD. And for AMD userptr driver, it is a SVM type driver, it has
> both interval tree and MMU notifier but userptr memory is moveable in
> it. No interval tree for Intel i386, not sure about the Intel XE driver.
>
> Maybe I can remove the interval tree in next version.
Great, thanks for the clarification. And no need to be sorry, it happens
to everyone on the ML :D
--
Best regards,
Dmitry
next prev parent reply other threads:[~2025-04-03 16:45 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 [this message]
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=4ca36f29-9a5d-4585-8699-f4e78dc7266e@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=Honglei1.Huang@amd.com \
--cc=airlied@redhat.com \
--cc=demiobenour@gmail.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®