diff options
| author | Matthew Auld <matthew.auld@intel.com> | 2026-06-26 12:15:30 +0100 |
|---|---|---|
| committer | Matthew Auld <matthew.auld@intel.com> | 2026-07-10 12:50:22 +0100 |
| commit | 85b42488f7689a5a7b5af28022ec11bb2984bd74 (patch) | |
| tree | 8623265084ce36de4713399826ab96548672a983 /tools/perf/scripts/python | |
| parent | fe0d94f65bf2fcc6fea930360d834b199a77e1c2 (diff) | |
drm/xe/hw_engine: document top-down paging requirement
We were doing this anyway, but going forward for paging engines,
agreement is to always reserve BCS instances in top down fashion. This
hopefully future proofs things for VFs, where in some low-level places
it might only have the physical BCS instance from the hw pov. If we
stick to a consistent mapping scheme, it should make it possible to
determine if this is a special paging engine, or not.
v2 (Daniele)
- Give a concrete example, like with page fault descriptor
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Link: https://patch.msgid.link/20260626111520.487997-21-matthew.auld@intel.com
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
