drm/xe: Rework instances of variants of xe_bo_create_locked()

Browse source

A common pattern is to create a locked bo, pin it without mapping
and then unlock it. Add a function to do that, which internally
uses xe_validation_guard().
With that we can remove xe_bo_create_locked_range() and add
exhaustive eviction to stolen, pf_provision_vf_lmem and
psmi_alloc_object.

v4:
- New patch after reorganization.
v5:
- Replace DRM_XE_GEM_CPU_CACHING_WB with 0. (CI)

Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
Link: https://lore.kernel.org/r/20250908101246.65025-13-thomas.hellstrom@linux.intel.com

...

This commit is contained in:

Thomas Hellström 2025-09-08 12:12:45 +02:00

parent 59eabff2a3

commit 1f1541720f

5 changed files with 70 additions and 87 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

13

drivers/gpu/drm/xe/compat-i915-headers/gem/i915_gem_stolen.h

View file

86

drivers/gpu/drm/xe/xe_bo.c

View file

9

drivers/gpu/drm/xe/xe_bo.h

View file

23

drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c

View file

26

drivers/gpu/drm/xe/xe_psmi.c

View file