From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>, intel-xe@lists.freedesktop.org
Cc: Francois Dugast <francois.dugast@intel.com>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Boris Brezillon <boris.brezillon@collabora.com>,
Danilo Krummrich <dakr@redhat.com>,
Linux DRI Development <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel@ffwll.ch>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-xe] [PATCH v4] Documentation/gpu: VM_BIND locking document
Date: Fri, 17 Nov 2023 09:33:08 +0100 [thread overview]
Message-ID: <a1cbe3e8-2b2c-150a-7919-65bdd38f75be@linux.intel.com> (raw)
In-Reply-To: <ZVYVk8KutkQE0RDU@archie.me>
Hi,
On 11/16/23 14:13, Bagas Sanjaya wrote:
> On Wed, Nov 15, 2023 at 01:49:37PM +0100, Thomas Hellström wrote:
>> +TODO: Pointer to the gpuvm code implementation if this iteration and
> "... implementation of this iteration ..."
>
>> +Using a MMU notifier for device DMA (and other methods) is described in
>> +`this document
>> +<https://docs.kernel.org/core-api/pin_user_pages.html#case-3-mmu-notifier-registration-with-or-without-page-faulting-hardware>`_.
> You can use internal linking instead:
>
> ---- >8 ----
> diff --git a/Documentation/core-api/pin_user_pages.rst b/Documentation/core-api/pin_user_pages.rst
> index d3c1f6d8c0e0ec..6b5f7e6e7155fb 100644
> --- a/Documentation/core-api/pin_user_pages.rst
> +++ b/Documentation/core-api/pin_user_pages.rst
> @@ -153,6 +153,8 @@ NOTE: Some pages, such as DAX pages, cannot be pinned with longterm pins. That's
> because DAX pages do not have a separate page cache, and so "pinning" implies
> locking down file system blocks, which is not (yet) supported in that way.
>
> +.. _mmu-notifier-registration-case:
> +
> CASE 3: MMU notifier registration, with or without page faulting hardware
> -------------------------------------------------------------------------
> Device drivers can pin pages via get_user_pages*(), and register for mmu
> diff --git a/Documentation/gpu/drm-vm-bind-locking.rst b/Documentation/gpu/drm-vm-bind-locking.rst
> index bc701157cb3414..08b6a47a6e592f 100644
> --- a/Documentation/gpu/drm-vm-bind-locking.rst
> +++ b/Documentation/gpu/drm-vm-bind-locking.rst
> @@ -366,8 +366,7 @@ need to care about, but so far it has proven difficult to exclude
> certain notifications.
>
> Using a MMU notifier for device DMA (and other methods) is described in
> -`this document
> -<https://docs.kernel.org/core-api/pin_user_pages.html#case-3-mmu-notifier-registration-with-or-without-page-faulting-hardware>`_.
> +:ref:`pin_user_pages() documentation <mmu-notifier-registration-case>`.
>
> Now the method of obtaining struct page references using
> get_user_pages() unfortunately can't be used under a dma_resv lock
>
> Thanks.
>
Thanks. I'll take a look at doing this as well.
Thomas
WARNING: multiple messages have this Message-ID (diff)
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>, intel-xe@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>,
Matthew Brost <matthew.brost@intel.com>,
Danilo Krummrich <dakr@redhat.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>,
Linux DRI Development <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v4] Documentation/gpu: VM_BIND locking document
Date: Fri, 17 Nov 2023 09:33:08 +0100 [thread overview]
Message-ID: <a1cbe3e8-2b2c-150a-7919-65bdd38f75be@linux.intel.com> (raw)
In-Reply-To: <ZVYVk8KutkQE0RDU@archie.me>
Hi,
On 11/16/23 14:13, Bagas Sanjaya wrote:
> On Wed, Nov 15, 2023 at 01:49:37PM +0100, Thomas Hellström wrote:
>> +TODO: Pointer to the gpuvm code implementation if this iteration and
> "... implementation of this iteration ..."
>
>> +Using a MMU notifier for device DMA (and other methods) is described in
>> +`this document
>> +<https://docs.kernel.org/core-api/pin_user_pages.html#case-3-mmu-notifier-registration-with-or-without-page-faulting-hardware>`_.
> You can use internal linking instead:
>
> ---- >8 ----
> diff --git a/Documentation/core-api/pin_user_pages.rst b/Documentation/core-api/pin_user_pages.rst
> index d3c1f6d8c0e0ec..6b5f7e6e7155fb 100644
> --- a/Documentation/core-api/pin_user_pages.rst
> +++ b/Documentation/core-api/pin_user_pages.rst
> @@ -153,6 +153,8 @@ NOTE: Some pages, such as DAX pages, cannot be pinned with longterm pins. That's
> because DAX pages do not have a separate page cache, and so "pinning" implies
> locking down file system blocks, which is not (yet) supported in that way.
>
> +.. _mmu-notifier-registration-case:
> +
> CASE 3: MMU notifier registration, with or without page faulting hardware
> -------------------------------------------------------------------------
> Device drivers can pin pages via get_user_pages*(), and register for mmu
> diff --git a/Documentation/gpu/drm-vm-bind-locking.rst b/Documentation/gpu/drm-vm-bind-locking.rst
> index bc701157cb3414..08b6a47a6e592f 100644
> --- a/Documentation/gpu/drm-vm-bind-locking.rst
> +++ b/Documentation/gpu/drm-vm-bind-locking.rst
> @@ -366,8 +366,7 @@ need to care about, but so far it has proven difficult to exclude
> certain notifications.
>
> Using a MMU notifier for device DMA (and other methods) is described in
> -`this document
> -<https://docs.kernel.org/core-api/pin_user_pages.html#case-3-mmu-notifier-registration-with-or-without-page-faulting-hardware>`_.
> +:ref:`pin_user_pages() documentation <mmu-notifier-registration-case>`.
>
> Now the method of obtaining struct page references using
> get_user_pages() unfortunately can't be used under a dma_resv lock
>
> Thanks.
>
Thanks. I'll take a look at doing this as well.
Thomas
WARNING: multiple messages have this Message-ID (diff)
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>, intel-xe@lists.freedesktop.org
Cc: Matthew Brost <matthew.brost@intel.com>,
Francois Dugast <francois.dugast@intel.com>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Oak Zeng <oak.zeng@intel.com>,
Boris Brezillon <boris.brezillon@collabora.com>,
Danilo Krummrich <dakr@redhat.com>,
Linux DRI Development <dri-devel@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v4] Documentation/gpu: VM_BIND locking document
Date: Fri, 17 Nov 2023 09:33:08 +0100 [thread overview]
Message-ID: <a1cbe3e8-2b2c-150a-7919-65bdd38f75be@linux.intel.com> (raw)
In-Reply-To: <ZVYVk8KutkQE0RDU@archie.me>
Hi,
On 11/16/23 14:13, Bagas Sanjaya wrote:
> On Wed, Nov 15, 2023 at 01:49:37PM +0100, Thomas Hellström wrote:
>> +TODO: Pointer to the gpuvm code implementation if this iteration and
> "... implementation of this iteration ..."
>
>> +Using a MMU notifier for device DMA (and other methods) is described in
>> +`this document
>> +<https://docs.kernel.org/core-api/pin_user_pages.html#case-3-mmu-notifier-registration-with-or-without-page-faulting-hardware>`_.
> You can use internal linking instead:
>
> ---- >8 ----
> diff --git a/Documentation/core-api/pin_user_pages.rst b/Documentation/core-api/pin_user_pages.rst
> index d3c1f6d8c0e0ec..6b5f7e6e7155fb 100644
> --- a/Documentation/core-api/pin_user_pages.rst
> +++ b/Documentation/core-api/pin_user_pages.rst
> @@ -153,6 +153,8 @@ NOTE: Some pages, such as DAX pages, cannot be pinned with longterm pins. That's
> because DAX pages do not have a separate page cache, and so "pinning" implies
> locking down file system blocks, which is not (yet) supported in that way.
>
> +.. _mmu-notifier-registration-case:
> +
> CASE 3: MMU notifier registration, with or without page faulting hardware
> -------------------------------------------------------------------------
> Device drivers can pin pages via get_user_pages*(), and register for mmu
> diff --git a/Documentation/gpu/drm-vm-bind-locking.rst b/Documentation/gpu/drm-vm-bind-locking.rst
> index bc701157cb3414..08b6a47a6e592f 100644
> --- a/Documentation/gpu/drm-vm-bind-locking.rst
> +++ b/Documentation/gpu/drm-vm-bind-locking.rst
> @@ -366,8 +366,7 @@ need to care about, but so far it has proven difficult to exclude
> certain notifications.
>
> Using a MMU notifier for device DMA (and other methods) is described in
> -`this document
> -<https://docs.kernel.org/core-api/pin_user_pages.html#case-3-mmu-notifier-registration-with-or-without-page-faulting-hardware>`_.
> +:ref:`pin_user_pages() documentation <mmu-notifier-registration-case>`.
>
> Now the method of obtaining struct page references using
> get_user_pages() unfortunately can't be used under a dma_resv lock
>
> Thanks.
>
Thanks. I'll take a look at doing this as well.
Thomas
next prev parent reply other threads:[~2023-11-17 8:33 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 ` [Intel-xe] " Thomas Hellström
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 ` Thomas Hellström [this message]
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=a1cbe3e8-2b2c-150a-7919-65bdd38f75be@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=bagasdotme@gmail.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-doc@vger.kernel.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.