From: Matthew Brost <matthew.brost@intel.com>
To: John.C.Harrison@Intel.com
Cc: Intel-GFX@Lists.FreeDesktop.Org, DRI-Devel@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/guc: Report error on invalid reset notification
Date: Thu, 23 Dec 2021 09:58:20 -0800 [thread overview]
Message-ID: <20211223175820.GA3396@jons-linux-dev-box> (raw)
In-Reply-To: <20211223013128.1739792-1-John.C.Harrison@Intel.com>
On Wed, Dec 22, 2021 at 05:31:28PM -0800, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> Don't silently drop reset notifications from the GuC. It might not be
> safe to do an error capture but we still want some kind of report that
> the reset happened.
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
> ---
> drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> 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 e7517206af82..0fbf24b8d5e1 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> @@ -3979,6 +3979,11 @@ static void guc_handle_context_reset(struct intel_guc *guc,
> !context_blocked(ce))) {
> 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));
As discussed off the list, I'll a take an AR to see if we can not
supress the capture here. But until that gets resolved:
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> }
> }
>
> --
> 2.25.1
>
prev parent reply other threads:[~2021-12-23 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 1:31 [Intel-gfx] [PATCH] drm/i915/guc: Report error on invalid reset notification John.C.Harrison
2021-12-23 2:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-12-23 6:40 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-12-23 17:58 ` Matthew Brost [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=20211223175820.GA3396@jons-linux-dev-box \
--to=matthew.brost@intel.com \
--cc=DRI-Devel@Lists.FreeDesktop.Org \
--cc=Intel-GFX@Lists.FreeDesktop.Org \
--cc=John.C.Harrison@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