diff options
| author | Jonathan Cavitt <jonathan.cavitt@intel.com> | 2024-05-10 12:45:39 -0700 |
|---|---|---|
| committer | Matthew Brost <matthew.brost@intel.com> | 2024-05-14 16:28:52 -0700 |
| commit | abdea2847acfe41313620a5359940522990018e3 (patch) | |
| tree | 606d12f2f9f928cdaab953cf16ca7746379819eb /tools/lib/python | |
| parent | 1564d411e17f51e2f64655b4e4da015be1ba7eaa (diff) | |
drm/xe/xe_guc_submit: Allow lr exec queues to be banned
LR queues currently don't get banned during a GT/GuC reset because they
lack a job. Though they don't have a job to detect the reset status of,
it's still possible to tell when they should be banned by looking at the
LRC: if the LRC head and tail don't match, then the exec queue should be
banned and cleaned up.
This also requires swapping the usage of xe_sched_tdr_queue_imm with
xe_guc_exec_queue_trigger_cleanup, as the former is specific to non-lr
exec queues.
Suggested-by: Matthew Brost <matthew.brost@intel.com>
Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Stuart Summers <stuart.summers@intel.com>
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20240510194540.3246991-2-jonathan.cavitt@intel.com
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions
