Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Francois Dugast <francois.dugast@intel.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Boris Brezillon <boris.brezillon@collabora.com>,
	Danilo Krummrich <dakr@redhat.com>,
	Daniel Vetter <daniel@ffwll.ch>,
	intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH v3] Documentation/gpu: VM_BIND locking document
Date: Tue, 14 Nov 2023 16:25:58 +0100	[thread overview]
Message-ID: <716d4ec8-4c03-8eb5-a244-93bd1b89aced@linux.intel.com> (raw)
In-Reply-To: <ZUKw5DxOb5T48F+Q@intel.com>

[-- Attachment #1: Type: text/plain, Size: 978 bytes --]

Hi, Rodrigo

On 11/1/23 21:11, Rodrigo Vivi 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.
>>
>> v2:
>> - s/gvm/gpu_vm/g (Rodrigo Vivi)
>> - Clarify the userptr seqlock with a pointer to mm/mmu_notifier.c
>>    (Rodrigo Vivi)
>> - Adjust commit message accordingly.
>> - Add SPDX license header.
>>
>> v3:
>> - Large update to align with the drm_gpuvm manager locking
>> - Add "Efficient userptr gpu_vma exec function iteration" section
>> - Add "Locking at bind- and unbind time" section.
>>
>> Cc: Rodrigo Vivi<rodrigo.vivi@intel.com>
>> Signed-off-by: Thomas Hellström<thomas.hellstrom@linux.intel.com>

Thanks for the review comments. I'll address all these in a v4 shortly.

/Thomas


[-- Attachment #2: Type: text/html, Size: 1583 bytes --]

      reply	other threads:[~2023-11-14 15:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-22 18:02 [Intel-xe] [PATCH v3] Documentation/gpu: VM_BIND locking document Thomas Hellström
2023-10-24  7:02 ` [Intel-xe] ✗ CI.Patch_applied: failure for Documentation/gpu: VM_BIND locking document (rev2) Patchwork
2023-10-31 22:01 ` [Intel-xe] [PATCH v3] Documentation/gpu: VM_BIND locking document Rodrigo Vivi
2023-11-01 20:11 ` Rodrigo Vivi
2023-11-14 15:25   ` Thomas Hellström [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=716d4ec8-4c03-8eb5-a244-93bd1b89aced@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=boris.brezillon@collabora.com \
    --cc=dakr@redhat.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=francois.dugast@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rodrigo.vivi@intel.com \
    /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