From: Nareshkumar Gollakoti <naresh.kumar.g@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: himal.prasad.ghimiray@intel.com, naresh.kumar.g@intel.com
Subject: [PATCH v3 0/8] drm/xe:add page size allocation mode control and coverage
Date: Sun, 12 Jul 2026 16:45:09 +0530 [thread overview]
Message-ID: <20260712111517.1956177-1-naresh.kumar.g@intel.com> (raw)
Some platforms support multiple page sizes for user BO allocations,
including 4K, 64K, 2M, and 1G.
For validation and debug, it is useful to control the page size
selection policy for user BOs so that specific allocation paths can be
exercised deterministically. In particular, this makes it possible to
force allocations into 2M-only, 1G-only, or mixed modes.
In mixed mode, allocations are distributed across the supported page
sizes in a round-robin manner. For example, for four user BOs, the
selected page sizes would be:
- BO1: 4K
- BO2: 64K
- BO3: 2M
- BO4: 1G
This series adds debug page-size allocation control for user BO in xe
This series includes:
- debug control state in xe_device
- a debugfs knob to select allocation mode
- add Kconfig option for debug page-size allocation control
- 1G BO alignment flag handling
- debug policy application at user BO create time
- propagation into VMA map flags
- PT bind support for selecting leaf level (4K/64K, 2M, 1G paths)
- add live Kunit coverage for BO page size allocation
The default path is unchanged when the debug control is not enabled.
v2
-- addressed v1 comments at
https://patchwork.freedesktop.org/series/169640/
v3
- refactor the design
- update patches based on review feedback
Nareshkumar Gollakoti (8):
drm/xe: add page size allocation control state to xe_device
drm/xe/debugfs: add page-size allocation mode knob
drm/xe: add Kconfig option for debug page-size allocation control
drm/xe: add XE_BO_FLAG_NEEDS_1G for minimum page-size sizing
drm/xe: apply debug page-size allocation policy to user BOs
drm/xe/vm: propagate BO page-size requirements to VMA map flags
drm/xe/pt: allow selecting the bind leaf PTE level
drm/xe/tests: add live KUnit coverage for BO page-size allocation
modes
drivers/gpu/drm/xe/Kconfig.debug | 17 ++
drivers/gpu/drm/xe/tests/xe_bo.c | 234 ++++++++++++++++++++
drivers/gpu/drm/xe/tests/xe_live_test_mod.c | 2 +
drivers/gpu/drm/xe/xe_bo.c | 91 +++++++-
drivers/gpu/drm/xe/xe_bo.h | 1 +
drivers/gpu/drm/xe/xe_debugfs.c | 61 +++++
drivers/gpu/drm/xe/xe_device.c | 9 +
drivers/gpu/drm/xe/xe_device_types.h | 25 +++
drivers/gpu/drm/xe/xe_pt.c | 25 ++-
drivers/gpu/drm/xe/xe_vm.c | 25 +++
10 files changed, 486 insertions(+), 4 deletions(-)
--
2.43.0
next reply other threads:[~2026-07-12 11:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 11:15 Nareshkumar Gollakoti [this message]
2026-07-12 11:15 ` [PATCH v3 1/8] drm/xe: add page size allocation control state to xe_device Nareshkumar Gollakoti
2026-07-12 11:15 ` [PATCH v3 2/8] drm/xe/debugfs: add page-size allocation mode knob Nareshkumar Gollakoti
2026-07-12 11:15 ` [PATCH v3 3/8] drm/xe: add Kconfig option for debug page-size allocation control Nareshkumar Gollakoti
2026-07-12 11:15 ` [PATCH v3 4/8] drm/xe: add XE_BO_FLAG_NEEDS_1G for minimum page-size sizing Nareshkumar Gollakoti
2026-07-12 11:15 ` [PATCH v3 5/8] drm/xe: apply debug page-size allocation policy to user BOs Nareshkumar Gollakoti
2026-07-12 11:15 ` [PATCH v3 6/8] drm/xe/vm: propagate BO page-size requirements to VMA map flags Nareshkumar Gollakoti
2026-07-12 11:15 ` [PATCH v3 7/8] drm/xe/pt: allow selecting the bind leaf PTE level Nareshkumar Gollakoti
2026-07-12 11:15 ` [PATCH v3 8/8] drm/xe/tests: add live KUnit coverage for BO page-size allocation modes Nareshkumar Gollakoti
2026-07-12 11:21 ` ✗ CI.checkpatch: warning for drm/xe:add page size allocation mode control and coverage Patchwork
2026-07-12 11:22 ` ✓ CI.KUnit: success " Patchwork
2026-07-13 4:46 ` [PATCH v3 0/8] " Simon Richter
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=20260712111517.1956177-1-naresh.kumar.g@intel.com \
--to=naresh.kumar.g@intel.com \
--cc=himal.prasad.ghimiray@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