mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
synced 2026-09-16 08:19:29 -05:00
Nareshkumar Gollakoti
6bea40fc4c
Introduce xe_page_size_alloc_ctrl_mode and add page_size_alloc_ctrl state to struct xe_device along with mutex lock. The new control supports forcing user BO allocations to 2M pages, forcing them to 1G pages, or using a mixed round-robin mode across 4K, 64K, 2M, and 1G page sizes. Track the current mixed-mode index in xe_device so allocation policy can be applied consistently. v2 - make cur_index to atomic as update need in later patch to avoid race/concurency (sashiko) v3 - reworded comments - protect mode/index updates with a mutex for proper concurrency handling v4(sashiko) - move xe_debug_page_size_alloc_ctrl_init() before drm_dev_register(), so mutex and control states are initialized before any userspace visibility v5(Himal) - Guard all the debug page size policy code under CONFIG - Squash Kconfig patch to have Kconfig entry for DEBUG_PAGE_SIZE - Add inline to check debug page size support and exact mode configured if it is supported. v6 (fix CI build) v8 (Himal) - use drmm_mutex_init to avoid leak with mutex_init - call xe_debug_page_size_alloc_ctrl_init unconditionally - Add missed mixed mode check on xe_debug_page_size_mode_not_none check - Add xe_debug_page_size_mode_is_mixed() function v9 - make xe_debug_page_size_alloc_ctrl_init() return int - fail probe if drmm_mutex_init() for page_size_alloc_ctrl.lock fails Signed-off-by: Nareshkumar Gollakoti <naresh.kumar.g@intel.com> Reviewed-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com> Link: https://patch.msgid.link/20260729121843.1255891-2-naresh.kumar.g@intel.com Signed-off-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
131 lines
3.7 KiB
Plaintext
131 lines
3.7 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0-only
|
|
config DRM_XE_WERROR
|
|
bool "Force GCC to throw an error instead of a warning when compiling"
|
|
# As this may inadvertently break the build, only allow the user
|
|
# to shoot oneself in the foot iff they aim really hard
|
|
depends on EXPERT
|
|
# We use the dependency on !COMPILE_TEST to not be enabled in
|
|
# allmodconfig or allyesconfig configurations
|
|
depends on !COMPILE_TEST
|
|
default n
|
|
help
|
|
Add -Werror to the build flags for (and only for) xe.ko.
|
|
Do not enable this unless you are writing code for the xe.ko module.
|
|
|
|
Recommended for driver developers only.
|
|
|
|
If in doubt, say "N".
|
|
|
|
config DRM_XE_DEBUG
|
|
bool "Enable additional driver debugging"
|
|
depends on DRM_XE
|
|
depends on EXPERT
|
|
depends on !COMPILE_TEST
|
|
default n
|
|
help
|
|
Choose this option to turn on extra driver debugging that may affect
|
|
performance but will catch some internal issues.
|
|
|
|
Recommended for driver developers only.
|
|
|
|
If in doubt, say "N".
|
|
|
|
config DRM_XE_DEBUG_VM
|
|
bool "Enable extra VM debugging info"
|
|
default n
|
|
help
|
|
Enable extra VM debugging info
|
|
|
|
Recommended for driver developers only.
|
|
|
|
If in doubt, say "N".
|
|
|
|
config DRM_XE_DEBUG_SRIOV
|
|
bool "Enable extra SR-IOV debugging"
|
|
default n
|
|
imply DRM_XE_DEBUG_MEMIRQ
|
|
help
|
|
Enable extra SR-IOV debugging info.
|
|
|
|
Recommended for driver developers only.
|
|
|
|
If in doubt, say "N".
|
|
|
|
config DRM_XE_DEBUG_MEMIRQ
|
|
bool "Enable extra memirq debugging"
|
|
default n
|
|
help
|
|
Choose this option to enable additional debugging info for
|
|
memory based interrupts.
|
|
|
|
Recommended for driver developers only.
|
|
|
|
If in doubt, say "N".
|
|
|
|
config DRM_XE_DEBUG_MEM
|
|
bool "Enable passing SYS/VRAM addresses to user space"
|
|
default n
|
|
help
|
|
Pass object location through uapi. Intended for extended
|
|
testing and development only.
|
|
|
|
Recommended for driver developers only.
|
|
|
|
If in doubt, say "N".
|
|
|
|
config DRM_XE_KUNIT_TEST
|
|
tristate "KUnit tests for the drm xe driver" if !KUNIT_ALL_TESTS
|
|
depends on DRM_XE && KUNIT && DEBUG_FS
|
|
default KUNIT_ALL_TESTS
|
|
select DRM_EXPORT_FOR_TESTS if m
|
|
help
|
|
Choose this option to allow the driver to perform selftests under
|
|
the kunit framework
|
|
|
|
Recommended for driver developers only.
|
|
|
|
If in doubt, say "N".
|
|
|
|
config DRM_XE_DEBUG_PAGE_SIZE
|
|
bool "Enable debug control for user BO page-size allocation"
|
|
depends on DRM_XE_DEBUG && DEBUG_FS
|
|
help
|
|
Expose a debugfs knob to override user BO page-size allocation
|
|
handling for validation and debug. Supported modes include forced
|
|
2M, forced 1G, and a mixed mode that exercises 4K, 64K, 2M, and
|
|
1G page-size paths on platforms that support them.
|
|
|
|
This is an unstable debugfs interface intended for development and
|
|
validation only. Its layout, contents, and existence may change or
|
|
be removed at any time with no regression warranty.
|
|
|
|
Recommended for driver developers only.
|
|
If in doubt, say "N".
|
|
|
|
config DRM_XE_DEBUG_GUC
|
|
bool "Enable extra GuC related debug options"
|
|
depends on DRM_XE_DEBUG
|
|
default n
|
|
select STACKDEPOT
|
|
help
|
|
Choose this option when debugging guc issues.
|
|
The GuC log buffer is increased to the maximum allowed, which should
|
|
be large enough for complex issues. The tracking of FAST_REQ messages
|
|
is extended to include a record of the calling stack, which is then
|
|
dumped on a FAST_REQ error notification.
|
|
|
|
Recommended for driver developers only.
|
|
|
|
If in doubt, say "N".
|
|
|
|
config DRM_XE_USERPTR_INVAL_INJECT
|
|
bool "Inject userptr invalidation -EINVAL errors"
|
|
depends on DRM_GPUSVM
|
|
default n
|
|
help
|
|
Choose this option when debugging error paths that
|
|
are hit during checks for userptr invalidations.
|
|
|
|
Recommended for driver developers only.
|
|
If in doubt, say "N".
|