From: Francois Dugast <francois.dugast@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: [PATCH v8 0/4] Enable THP support in drm_pagemap
Date: Thu, 12 Mar 2026 16:16:25 +0100 [thread overview]
Message-ID: <20260312151726.1779566-1-francois.dugast@intel.com> (raw)
Use Balbir Singh's series for device-private THP support [1] and previous
preparation work in drm_pagemap [2] to add 2MB/THP support in xe. This leads
to significant performance improvements when using SVM with 2MB pages.
[1] https://lore.kernel.org/linux-mm/20251001065707.920170-1-balbirs@nvidia.com/
[2] https://patchwork.freedesktop.org/series/151754/
v2:
- rebase on top of multi-device SVM
- add drm_pagemap_cpages() with temporary patch
- address other feedback from Matt Brost on v1
v3:
The major change is to remove the dependency to the mm/huge_memory
helper migrate_device_split_page() that was called explicitely when
a 2M buddy allocation backed by a large folio would be later reused
for a smaller allocation (4K or 64K). Instead, the first 3 patches
provided by Matthew Brost ensure large folios are split at the time
of freeing.
v4:
- add order argument to folio_free callback
- send complete series to linux-mm and MM folks as requested (Zi Yan
and Andrew Morton) and cover letter to anyone receiving at least
one of the patches (Liam R. Howlett)
v5:
- update zone_device_page_init() in patch #1 to reinitialize large
zone device private folios
v6:
- fix drm_pagemap change in patch #1 to allow applying to 6.19 and
add some comments
v7:
- now that patch #1 is merged, rebase and resend for CI
v8:
- rebase on 7.0.0-rc3
Francois Dugast (3):
drm/pagemap: Unlock and put folios when possible
drm/pagemap: Add helper to access zone_device_data
drm/pagemap: Enable THP support for GPU memory migration
Matthew Brost (1):
drm/pagemap: Correct cpages calculation for migrate_vma_setup
drivers/gpu/drm/drm_gpusvm.c | 7 +-
drivers/gpu/drm/drm_pagemap.c | 157 +++++++++++++++++++++++++++-------
include/drm/drm_pagemap.h | 14 +++
3 files changed, 147 insertions(+), 31 deletions(-)
--
2.43.0
next reply other threads:[~2026-03-12 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 15:16 Francois Dugast [this message]
2026-03-12 15:16 ` [PATCH v8 1/4] drm/pagemap: Unlock and put folios when possible Francois Dugast
2026-03-13 4:02 ` Claude review: " Claude Code Review Bot
2026-03-12 15:16 ` [PATCH v8 2/4] drm/pagemap: Add helper to access zone_device_data Francois Dugast
2026-03-13 4:02 ` Claude review: " Claude Code Review Bot
2026-03-12 15:16 ` [PATCH v8 3/4] drm/pagemap: Correct cpages calculation for migrate_vma_setup Francois Dugast
2026-03-13 4:02 ` Claude review: " Claude Code Review Bot
2026-03-12 15:16 ` [PATCH v8 4/4] drm/pagemap: Enable THP support for GPU memory migration Francois Dugast
2026-03-13 4:02 ` Claude review: " Claude Code Review Bot
2026-03-13 4:02 ` Claude review: Enable THP support in drm_pagemap Claude Code Review Bot
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=20260312151726.1779566-1-francois.dugast@intel.com \
--to=francois.dugast@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
/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