From: John Harrison <john.c.harrison@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
<Intel-GFX@Lists.FreeDesktop.Org>
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/guc: Suppress 'ignoring reset notification' message
Date: Thu, 12 Oct 2023 10:56:28 -0700 [thread overview]
Message-ID: <fa9ed09c-7590-4054-850b-eda61e068785@intel.com> (raw)
In-Reply-To: <a13a3cc3-3aca-3a67-637c-01f46f1173a5@linux.intel.com>
On 10/12/2023 03:21, Tvrtko Ursulin wrote:
> On 21/09/2023 19:20, John.C.Harrison@Intel.com wrote:
>> From: John Harrison <John.C.Harrison@Intel.com>
>>
>> If an active context has been banned (e.g. Ctrl+C killed) then it is
>> likely to be reset as part of evicting it from the hardware. That
>> results in a 'ignoring context reset notification: banned = 1'
>> message at info level. This confuses/concerns people and makes them
>> thing something has gone wrong when it hasn't.
>
> Noticed the "confuses/concerns people" part while preparing the 6.7
> pull request, and the fact there is no Fixes: tag. Is this something
> that would be worth sending to stable (manually and if yes could you
> do that please? If there were actual user bugs filed I guess.
>
No upstream bugs that I am aware of. There were very occasional
concerned emails from internal test teams (E2E and such rather than
kernel) and I think one internal bug was logged about it being seen when
running some automated user interaction stress test thing (monkey runner
or similar). So not sure that it is worth the effort of a backport to
older trees. And you can't really call it a bug with an older patch. The
message was never an error or even a warning, just an info level.
John.
> Regards,
>
> Tvrtko
>
>> There is already a debug level message with essentially the same
>> information. So drop the 'ignore' info level one and just add the
>> 'ignore' flag to the debug level one instead (which will therefore not
>> appear by default but will still show up in CI runs).
>>
>> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
>> ---
>> drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 10 +++++-----
>> 1 file changed, 5 insertions(+), 5 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 cabdc645fcddb..da7331346df1f 100644
>> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
>> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
>> @@ -4770,19 +4770,19 @@ static void guc_context_replay(struct
>> intel_context *ce)
>> static void guc_handle_context_reset(struct intel_guc *guc,
>> struct intel_context *ce)
>> {
>> + bool capture = intel_context_is_schedulable(ce);
>> +
>> trace_intel_context_reset(ce);
>> - guc_dbg(guc, "Got context reset notification: 0x%04X on %s,
>> exiting = %s, banned = %s\n",
>> + guc_dbg(guc, "%s context reset notification: 0x%04X on %s,
>> exiting = %s, banned = %s\n",
>> + capture ? "Got" : "Ignoring",
>> ce->guc_id.id, ce->engine->name,
>> str_yes_no(intel_context_is_exiting(ce)),
>> str_yes_no(intel_context_is_banned(ce)));
>> - if (likely(intel_context_is_schedulable(ce))) {
>> + if (capture) {
>> capture_error_state(guc, ce);
>> guc_context_replay(ce);
>> - } else {
>> - guc_info(guc, "Ignoring context reset notification of
>> exiting context 0x%04X on %s",
>> - ce->guc_id.id, ce->engine->name);
>> }
>> }
prev parent reply other threads:[~2023-10-12 17:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 18:20 [Intel-gfx] [PATCH] drm/i915/guc: Suppress 'ignoring reset notification' message John.C.Harrison
2023-09-22 5:25 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-09-23 2:11 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-09-25 14:23 ` [Intel-gfx] [PATCH] " Andi Shyti
2023-10-12 10:21 ` Tvrtko Ursulin
2023-10-12 17:56 ` 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=fa9ed09c-7590-4054-850b-eda61e068785@intel.com \
--to=john.c.harrison@intel.com \
--cc=DRI-Devel@Lists.FreeDesktop.Org \
--cc=Intel-GFX@Lists.FreeDesktop.Org \
--cc=tvrtko.ursulin@linux.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