iv/linux
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

drm/i915/guc: Do not complain about stale reset notifications

Browse Source 
It is possible for reset notifications to arrive for a context that is
in the process of being banned. So don't flag these as an error, just
report it as informational (because it is still useful to know that
resets are happening even if they are being ignored).

v2: Better wording for the message (review feedback from Tvrtko).
v3: Fix rebase issue (review feedback from Daniele).

Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20220225015232.1939497-1-John.C.Harrison@Intel.com
This commit is contained in:
John Harrison 2022-02-24 17:52:32 -08:00
parent e068ef3fd5
commit e2a1e7abae
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
View File

@ -4023,10 +4023,9 @@ static void guc_handle_context_reset(struct intel_guc *guc,
capture_error_state(guc, ce);
guc_context_replay(ce);
} else {
drm_err(&guc_to_gt(guc)->i915->drm,
"Invalid GuC engine reset notificaion for 0x%04X on %s: banned = %d, blocked = %d",
ce->guc_id.id, ce->engine->name, intel_context_is_banned(ce),
context_blocked(ce));
drm_info(&guc_to_gt(guc)->i915->drm,
"Ignoring context reset notification of banned context 0x%04X on %s",
ce->guc_id.id, ce->engine->name);
}
}