From: John Harrison <john.c.harrison@intel.com>
To: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>,
<Intel-GFX@Lists.FreeDesktop.Org>
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915/guc: Do not complain about stale reset notifications
Date: Tue, 22 Feb 2022 17:51:18 -0800 [thread overview]
Message-ID: <c96c52d1-28ec-8a85-0ea0-209601b0b2a7@intel.com> (raw)
In-Reply-To: <f99a6caf-7aeb-9ff4-4872-cc986e11cf66@intel.com>
On 2/22/2022 17:39, Ceraolo Spurio, Daniele wrote:
> On 2/11/2022 5:04 PM, John.C.Harrison@Intel.com wrote:
>> From: John Harrison <John.C.Harrison@Intel.com>
>>
>> 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).
>>
>> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
>> ---
>> drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 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 b3a429a92c0d..3afff24b8f24 100644
>> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
>> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
>> @@ -4022,10 +4022,10 @@ 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 for 0x%04X on %s:
>> banned = %d, blocked = %d",
>
> The if statement above checks for !banned, so if we're here we're
> banned for sure, no need to print it as if it was conditional. I'd
> reword it as something like: "Ignoring reset notification for banned
> context 0x%04X ...". With that:
Hmm. The patch was based on an older tree that had an extra term in the
if. Seems like the patch applied cleanly and I didn't check the
surrounding code! Will update it to drop the banned and blocked values.
John.
>
> Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>
> Daniele
>
>> + ce->guc_id.id, ce->engine->name,
>> intel_context_is_banned(ce),
>> + context_blocked(ce));
>> }
>> }
>
prev parent reply other threads:[~2022-02-23 1:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 1:04 [Intel-gfx] [PATCH v2] drm/i915/guc: Do not complain about stale reset notifications John.C.Harrison
2022-02-12 1:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/guc: Do not complain about stale reset notifications (rev2) Patchwork
2022-02-12 4:37 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-02-23 1:39 ` [Intel-gfx] [PATCH v2] drm/i915/guc: Do not complain about stale reset notifications Ceraolo Spurio, Daniele
2022-02-23 1:51 ` John Harrison [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c96c52d1-28ec-8a85-0ea0-209601b0b2a7@intel.com \
--to=john.c.harrison@intel.com \
--cc=DRI-Devel@Lists.FreeDesktop.Org \
--cc=Intel-GFX@Lists.FreeDesktop.Org \
--cc=daniele.ceraolospurio@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox