summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/flamegraph.py
diff options
context:
space:
mode:
authorPiotr Piórkowski <piotr.piorkowski@intel.com>2025-10-03 18:26:16 +0200
committerMichal Wajdeczko <michal.wajdeczko@intel.com>2025-10-06 08:33:48 +0200
commit9d290ab0b5a054cf5bb39a80b90140fa22704f61 (patch)
tree368b552703536b0fb632a3cb8979513e4cebe8bf /tools/perf/scripts/python/flamegraph.py
parentdb7dde99049f04b99cbf518be3a189b3e9f5c1d8 (diff)
downloadlinux-9d290ab0b5a054cf5bb39a80b90140fa22704f61.tar.gz
linux-9d290ab0b5a054cf5bb39a80b90140fa22704f61.zip
drm/xe: Introduce new BO flag XE_BO_FLAG_FORCE_USER_VRAM
When using a separate VRAM region for kernel allocations, some kernel structures, such as context userspace data, should not reside in the VRAM region dedicated to the kernel. The VRAM kernel region is intended only for allocations necessary for driver operation. Allocations created via ioctl are long-lived and not easily evictable. If this region runs out of space, there may not be a fallback, which could cause failures. To prevent this, add a new BO flag that explicitly forces the BO to be allocated in the general-purpose VRAM region accessible to userspace, avoiding the kernel-only VRAM region. v2: - update commit message (Matthew) Signed-off-by: Piotr Piórkowski <piotr.piorkowski@intel.com> Cc: Matthew Auld <matthew.auld@intel.com> Reviewed-by: Matthew Auld <matthew.auld@intel.com> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com> Link: https://lore.kernel.org/r/20251003162619.1984236-3-piotr.piorkowski@intel.com
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions