From: Brian Nguyen <brian3.nguyen@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Brian Nguyen <brian3.nguyen@intel.com>
Subject: [PATCH v4 0/3] Page Reclamation Fixes
Date: Thu, 5 Mar 2026 17:15:47 +0000 [thread overview]
Message-ID: <20260305171546.67691-5-brian3.nguyen@intel.com> (raw)
A few changes to the page reclamation code. Fix up the PRL generation and
move the page reclaim done handler to its own function.
Thanks,
Brian
v2:
- Update non-leaf handling.
- Re-add assert for non-leaf.git
v3:
- Modify secondary PRL abort to check non-leaf levels. (Matthew B)
- In the case of NULL VMA, there should be no corresponding
PRL entry, so leverage existing skip logic to skip over.
v4:
- Rebase to get CI results.
Brian Nguyen (3):
drm/xe: Skip over non leaf pte for PRL generation
drm/xe: Move page reclaim done_handler to own func
drm/xe: Skip adding PRL entry to NULL VMA
drivers/gpu/drm/xe/xe_guc_ct.c | 23 ++++++-----------
drivers/gpu/drm/xe/xe_page_reclaim.c | 26 +++++++++++++++++++
drivers/gpu/drm/xe/xe_page_reclaim.h | 3 +++
drivers/gpu/drm/xe/xe_pt.c | 38 +++++++++++++++++++++-------
4 files changed, 66 insertions(+), 24 deletions(-)
--
2.43.0
next reply other threads:[~2026-03-05 17:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 17:15 Brian Nguyen [this message]
2026-03-05 17:15 ` [PATCH v4 1/3] drm/xe: Skip over non leaf pte for PRL generation Brian Nguyen
2026-03-05 17:15 ` [PATCH v4 2/3] drm/xe: Move page reclaim done_handler to own func Brian Nguyen
2026-03-05 17:15 ` [PATCH v4 3/3] drm/xe: Skip adding PRL entry to NULL VMA Brian Nguyen
2026-03-06 15:33 ` ✓ CI.KUnit: success for Page Reclamation Fixes (rev4) Patchwork
2026-03-06 16:36 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-03-07 1:53 ` ✓ CI.KUnit: success for Page Reclamation Fixes (rev5) Patchwork
2026-03-07 2:46 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-08 5:33 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-11 18:14 ` Nguyen, Brian
2026-03-16 16:44 ` Matt Roper
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=20260305171546.67691-5-brian3.nguyen@intel.com \
--to=brian3.nguyen@intel.com \
--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