diff options
author | John Harrison <John.C.Harrison@Intel.com> | 2023-01-27 01:28:41 +0100 |
---|---|---|
committer | John Harrison <John.C.Harrison@Intel.com> | 2023-01-27 22:01:24 +0100 |
commit | e9823f0fc375b87a461faaaeea886491660b3083 (patch) | |
tree | d7d894e1c4c3c589ed9a06b95c81e83d1d796b53 /drivers | |
parent | drm/i915/guc: Look for a guilty context when an engine reset fails (diff) | |
download | linux-e9823f0fc375b87a461faaaeea886491660b3083.tar.xz linux-e9823f0fc375b87a461faaaeea886491660b3083.zip |
drm/i915/guc: Add a debug print on GuC triggered reset
For understanding bug reports, it can be useful to have an explicit
dmesg print when a reset notification is received from GuC. As opposed
to simply inferring that this happened from other messages.
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20230127002842.3169194-8-John.C.Harrison@Intel.com
Diffstat (limited to 'drivers')
-rw-r--r-- | drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c index 7adc35bd4435..2e6ab0bb5c2b 100644 --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c @@ -4666,6 +4666,10 @@ static void guc_handle_context_reset(struct intel_guc *guc, { trace_intel_context_reset(ce); + drm_dbg(&guc_to_gt(guc)->i915->drm, "Got GuC reset of 0x%04X, exiting = %d, banned = %d\n", + ce->guc_id.id, test_bit(CONTEXT_EXITING, &ce->flags), + test_bit(CONTEXT_BANNED, &ce->flags)); + if (likely(intel_context_is_schedulable(ce))) { capture_error_state(guc, ce); guc_context_replay(ce); |