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

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

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 b0de9110884a4852363bb863d02040960a69f976..810910e8042ea26631da90c96b83aeef46950265 100644 (file)
--- a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
+++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
@@ -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);
        }
 }