[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <720d1b54-0898-1fbc-b1a0-338782e0e485@linux.intel.com>
Date: Wed, 29 Nov 2023 20:36:37 +0100
From: Thomas Hellström
<thomas.hellstrom@...ux.intel.com>
To: John Hubbard <jhubbard@...dia.com>, intel-xe@...ts.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@...el.com>,
Boris Brezillon <boris.brezillon@...labora.com>,
Danilo Krummrich <dakr@...hat.com>,
Matthew Brost <matthew.brost@...el.com>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
Oak Zeng <oak.zeng@...el.com>, Daniel Vetter <daniel@...ll.ch>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Francois Dugast <francois.dugast@...el.com>,
dri-devel@...ts.freedesktop.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6] Documentation/gpu: VM_BIND locking document
On 11/29/23 20:20, John Hubbard wrote:
> On 11/29/23 01:06, Thomas Hellström wrote:
>> Add the first version of the VM_BIND locking document which is
>> intended to be part of the xe driver upstreaming agreement.
>>
>> The document describes and discuss the locking used during exec-
>> functions, evicton and for userptr gpu-vmas. Intention is to be using
>> the
>> same nomenclature as the drm-vm-bind-async.rst.
>>
>
> Hi Thomas,
>
> As requested, for the pin_user_pages() aspects (the MMU notifier
> registration case), please feel free to add:
>
> Acked-by: John Hubbard <jhubbard@...dia.com
>
> thanks,
Hi, John,
Thanks!
/Thomas
Powered by blists - more mailing lists