From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Brost <matthew.brost@intel.com>,
intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: francois.dugast@intel.com, himal.prasad.ghimiray@intel.com
Subject: Re: [PATCH] drm/gpusvm, pagemap: Do not assume DRM pagemap owns device pages
Date: Fri, 17 Apr 2026 13:42:09 +0200 [thread overview]
Message-ID: <aff8ca0727ba41ca69f3e8c8255a33219727b4be.camel@linux.intel.com> (raw)
In-Reply-To: <20260409015512.3670302-1-matthew.brost@intel.com>
On Wed, 2026-04-08 at 18:55 -0700, Matthew Brost wrote:
> Update drm_pagemap_page_zone_device_data() to derive the pgmap ops
> from
> the page and compare them against the DRM pagemap ops. If the ops do
> not
> match, return NULL.
>
> Also harden two risky call sites by checking for NULL after
> hmm_range_fault() or migrate_vma_setup() when migrating to device
> memory, as it is possible to encounter device pages that are not
> owned
> by DRM pagemap.
>
> Suggested-by: sashiko.dev
Is there a proper (fake) email we can use?
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/drm_gpusvm.c | 5 +++++
> drivers/gpu/drm/drm_pagemap.c | 14 ++++++++++----
> include/drm/drm_pagemap.h | 5 ++++-
> 3 files changed, 19 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_gpusvm.c
> b/drivers/gpu/drm/drm_gpusvm.c
> index 365a9c0b522a..b3cccd047a21 100644
> --- a/drivers/gpu/drm/drm_gpusvm.c
> +++ b/drivers/gpu/drm/drm_gpusvm.c
> @@ -1506,6 +1506,11 @@ int drm_gpusvm_get_pages(struct drm_gpusvm
> *gpusvm,
> struct drm_pagemap_zdd *__zdd =
> drm_pagemap_page_zone_device_data(pa
> ge);
>
> + if (!__zdd) {
> + err = -EINVAL;
> + goto err_unmap;
> + }
> +
Here, __zdd is never dereferenced. As I understand it, the current
behaviour (before this patch) is that pages from mixed pagemaps are
generating an -EOPNOTSUPP, re-trying migration, which I think is the
correct behaviour, save possibly for foreign device-coherent pages.
Also see below reasoning WRT "owner".
> if (!ctx->allow_mixed &&
> zdd != __zdd && i > 0) {
> err = -EOPNOTSUPP;
> diff --git a/drivers/gpu/drm/drm_pagemap.c
> b/drivers/gpu/drm/drm_pagemap.c
> index d82ea7ccb8da..95c951c5b569 100644
> --- a/drivers/gpu/drm/drm_pagemap.c
> +++ b/drivers/gpu/drm/drm_pagemap.c
> @@ -753,10 +753,16 @@ int drm_pagemap_migrate_to_devmem(struct
> drm_pagemap_devmem *devmem_allocation,
> own_pages++;
> goto next;
> }
> - cur.dpagemap = src_zdd->dpagemap;
> - cur.ops = src_zdd->devmem_allocation->ops;
> - cur.device = cur.dpagemap->drm->dev;
> - pages[i] = src_page;
> + if (src_zdd) {
> + cur.dpagemap = src_zdd->dpagemap;
> + cur.ops = src_zdd-
> >devmem_allocation->ops;
> + cur.device = cur.dpagemap->drm->dev;
> + pages[i] = src_page;
> + } else {
This shouldn't happen, because we select device_private pages based on
dev_private owner. IMO we shouldn't allow non drm_pagemap
device_private pages sharing owner because we wouldn't now how to
migrate them.
> + npages = i;
> + err = -EINVAL;
> + goto err_finalize;
> + }
> }
> if (!pages[i]) {
> cur.dpagemap = NULL;
> diff --git a/include/drm/drm_pagemap.h b/include/drm/drm_pagemap.h
> index 95eb4b66b057..9b7c50932db5 100644
> --- a/include/drm/drm_pagemap.h
> +++ b/include/drm/drm_pagemap.h
> @@ -367,12 +367,15 @@ int drm_pagemap_reinit(struct drm_pagemap
> *dpagemap);
> * drm_pagemap_page_zone_device_data() - Page to zone_device_data
> * @page: Pointer to the page
> *
> - * Return: Page's zone_device_data
> + * Return: Page's zone_device_data if owned by DRM pagemap, NULL
> otherwise
> */
> static inline struct drm_pagemap_zdd
> *drm_pagemap_page_zone_device_data(struct page *page)
> {
> struct folio *folio = page_folio(page);
>
> + if (WARN_ON_ONCE(page_pgmap(page)->ops !=
> drm_pagemap_pagemap_ops_get()))
Driver could be handing a separate ops. Like if we wanted to check for
wedging / unplug before trying to migrate back to system, so this
wouldn't work.
So in general I don't think this patch is correct. Perhaps we should
look at updating the docs around owner assignment, though and also
perhaps make drm_gpusvm_get_pages() a bit more permissive?
/Thomas
> + return NULL;
> +
> return folio_zone_device_data(folio);
> }
>
prev parent reply other threads:[~2026-04-17 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 1:55 [PATCH] drm/gpusvm, pagemap: Do not assume DRM pagemap owns device pages Matthew Brost
2026-04-10 12:46 ` [PATCH] drm/gpusvm,pagemap: " Francois Dugast
2026-04-10 20:02 ` Matthew Brost
2026-04-11 9:06 ` Francois Dugast
2026-04-17 11:42 ` 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=aff8ca0727ba41ca69f3e8c8255a33219727b4be.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=francois.dugast@intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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