From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Danilo Krummrich <dakr@redhat.com>
Cc: Francois Dugast <francois.dugast@intel.com>,
linux-kernel@vger.kernel.org,
Boris Brezillon <boris.brezillon@collabora.com>,
dri-devel@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH v4] Documentation/gpu: VM_BIND locking document
Date: Wed, 15 Nov 2023 17:04:33 +0100 [thread overview]
Message-ID: <62cdf31f6dbbb3a114755affc89d22fde875c3ff.camel@linux.intel.com> (raw)
In-Reply-To: <ZVTfmbDz1HGqt4Ef@pollux>
Hi, Danilo,
On Wed, 2023-11-15 at 16:11 +0100, Danilo Krummrich wrote:
> On Wed, Nov 15, 2023 at 01:49:37PM +0100, 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.
> >
Thanks for reviewing. I'll update the document accordingly except for
the s/an rwsem/a rwsem/g, I think it's "an rwsem" similarly to "an r".
/Thomas
WARNING: multiple messages have this Message-ID (diff)
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Danilo Krummrich <dakr@redhat.com>
Cc: Matthew Brost <matthew.brost@intel.com>,
Francois Dugast <francois.dugast@intel.com>,
linux-kernel@vger.kernel.org, Oak Zeng <oak.zeng@intel.com>,
Boris Brezillon <boris.brezillon@collabora.com>,
dri-devel@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v4] Documentation/gpu: VM_BIND locking document
Date: Wed, 15 Nov 2023 17:04:33 +0100 [thread overview]
Message-ID: <62cdf31f6dbbb3a114755affc89d22fde875c3ff.camel@linux.intel.com> (raw)
In-Reply-To: <ZVTfmbDz1HGqt4Ef@pollux>
Hi, Danilo,
On Wed, 2023-11-15 at 16:11 +0100, Danilo Krummrich wrote:
> On Wed, Nov 15, 2023 at 01:49:37PM +0100, 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.
> >
Thanks for reviewing. I'll update the document accordingly except for
the s/an rwsem/a rwsem/g, I think it's "an rwsem" similarly to "an r".
/Thomas
WARNING: multiple messages have this Message-ID (diff)
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Danilo Krummrich <dakr@redhat.com>
Cc: intel-xe@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Matthew Brost <matthew.brost@intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Oak Zeng <oak.zeng@intel.com>, Daniel Vetter <daniel@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Francois Dugast <francois.dugast@intel.com>,
Boris Brezillon <boris.brezillon@collabora.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] Documentation/gpu: VM_BIND locking document
Date: Wed, 15 Nov 2023 17:04:33 +0100 [thread overview]
Message-ID: <62cdf31f6dbbb3a114755affc89d22fde875c3ff.camel@linux.intel.com> (raw)
In-Reply-To: <ZVTfmbDz1HGqt4Ef@pollux>
Hi, Danilo,
On Wed, 2023-11-15 at 16:11 +0100, Danilo Krummrich wrote:
> On Wed, Nov 15, 2023 at 01:49:37PM +0100, 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.
> >
Thanks for reviewing. I'll update the document accordingly except for
the s/an rwsem/a rwsem/g, I think it's "an rwsem" similarly to "an r".
/Thomas
next prev parent reply other threads:[~2023-11-15 16:04 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 12:49 [Intel-xe] [PATCH v4] Documentation/gpu: VM_BIND locking document Thomas Hellström
2023-11-15 12:49 ` Thomas Hellström
2023-11-15 12:49 ` Thomas Hellström
2023-11-15 15:11 ` [Intel-xe] " Danilo Krummrich
2023-11-15 15:11 ` Danilo Krummrich
2023-11-15 15:11 ` Danilo Krummrich
2023-11-15 16:04 ` Thomas Hellström [this message]
2023-11-15 16:04 ` Thomas Hellström
2023-11-15 16:04 ` Thomas Hellström
2023-11-15 17:02 ` [Intel-xe] " Danilo Krummrich
2023-11-15 17:02 ` Danilo Krummrich
2023-11-15 17:02 ` Danilo Krummrich
2023-11-15 17:18 ` [Intel-xe] " Thomas Hellström
2023-11-15 17:18 ` Thomas Hellström
2023-11-15 17:18 ` Thomas Hellström
2023-11-15 17:30 ` [Intel-xe] ✗ CI.Patch_applied: failure for Documentation/gpu: VM_BIND locking document (rev3) Patchwork
2023-11-16 9:48 ` [Intel-xe] [PATCH v4] Documentation/gpu: VM_BIND locking document Boris Brezillon
2023-11-16 9:48 ` Boris Brezillon
2023-11-16 9:48 ` Boris Brezillon
2023-11-16 11:48 ` [Intel-xe] " Thomas Hellström
2023-11-16 11:48 ` Thomas Hellström
2023-11-16 11:48 ` Thomas Hellström
2023-11-16 13:27 ` [Intel-xe] " Boris Brezillon
2023-11-16 13:27 ` Boris Brezillon
2023-11-16 13:27 ` Boris Brezillon
2023-11-16 13:53 ` [Intel-xe] " Thomas Hellström
2023-11-16 13:53 ` Thomas Hellström
2023-11-16 13:53 ` Thomas Hellström
2023-11-16 14:47 ` [Intel-xe] " Boris Brezillon
2023-11-16 14:47 ` Boris Brezillon
2023-11-16 14:47 ` Boris Brezillon
2023-11-16 15:01 ` [Intel-xe] " Thomas Hellström
2023-11-16 15:01 ` Thomas Hellström
2023-11-16 15:01 ` Thomas Hellström
2023-11-21 8:41 ` [Intel-xe] " Thomas Hellström
2023-11-21 8:41 ` Thomas Hellström
2023-11-21 8:41 ` Thomas Hellström
2023-11-16 14:02 ` [Intel-xe] " Danilo Krummrich
2023-11-16 14:02 ` Danilo Krummrich
2023-11-16 14:02 ` Danilo Krummrich
2023-11-16 14:09 ` [Intel-xe] " Thomas Hellström
2023-11-16 14:09 ` Thomas Hellström
2023-11-16 14:09 ` Thomas Hellström
2023-11-16 13:13 ` [Intel-xe] " Bagas Sanjaya
2023-11-16 13:13 ` Bagas Sanjaya
2023-11-16 13:13 ` Bagas Sanjaya
2023-11-17 8:33 ` [Intel-xe] " Thomas Hellström
2023-11-17 8:33 ` Thomas Hellström
2023-11-17 8:33 ` Thomas Hellström
2023-11-16 13:16 ` [Intel-xe] ✗ CI.Patch_applied: failure for Documentation/gpu: VM_BIND locking document (rev4) Patchwork
2023-11-17 15:14 ` [Intel-xe] ✗ CI.Patch_applied: failure for Documentation/gpu: VM_BIND locking document (rev3) Patchwork
2023-11-18 2:22 ` [Intel-xe] ✗ CI.Patch_applied: failure for Documentation/gpu: VM_BIND locking document (rev4) Patchwork
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=62cdf31f6dbbb3a114755affc89d22fde875c3ff.camel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.