[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4ca36f29-9a5d-4585-8699-f4e78dc7266e@collabora.com>
Date: Thu, 3 Apr 2025 19:44:34 +0300
From: Dmitry Osipenko <dmitry.osipenko@...labora.com>
To: "Huang, Honglei1" <Honglei1.Huang@....com>,
Demi Marie Obenour <demiobenour@...il.com>, David Airlie
<airlied@...hat.com>, Gerd Hoffmann <kraxel@...hat.com>,
Gurchetan Singh <gurchetansingh@...omium.org>, Chia-I Wu
<olvaffe@...il.com>, Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>,
Simona Vetter <simona@...ll.ch>, Rob Clark <robdclark@...il.com>,
Huang Rui <ray.huang@....com>
Cc: dri-devel@...ts.freedesktop.org, virtualization@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 7/7] drm/virtio: implement userptr: add interval tree
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
Powered by blists - more mailing lists