From: John.C.Harrison@Intel.com
To: Intel-GFX@Lists.FreeDesktop.Org
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: [Intel-gfx] [PATCH 0/2] Allow error capture without a request / on reset failure
Date: Tue, 29 Nov 2022 13:12:51 -0800 [thread overview]
Message-ID: <20221129211253.3183480-1-John.C.Harrison@Intel.com> (raw)
From: John Harrison <John.C.Harrison@Intel.com>
It is technically possible to get a hung context without a valid
request. In such a situation, try to provide as much information in
the error capture as possible rather than just aborting and capturing
nothing.
Similarly, in the case of a engine reset failure the GuC is not able
to report the guilty context. So try a manual search instead of
reporting nothing.
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
John Harrison (2):
drm/i915: Allow error capture without a request
drm/i915/guc: Look for a guilty context when an engine reset fails
.../gpu/drm/i915/gt/uc/intel_guc_submission.c | 15 ++++-
drivers/gpu/drm/i915/i915_gpu_error.c | 55 ++++++++++++++-----
2 files changed, 54 insertions(+), 16 deletions(-)
--
2.37.3
next reply other threads:[~2022-11-29 21:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 21:12 John.C.Harrison [this message]
2022-11-29 21:12 ` [Intel-gfx] [PATCH 1/2] drm/i915: Allow error capture without a request John.C.Harrison
2022-12-13 1:52 ` Umesh Nerlige Ramappa
2022-12-16 21:06 ` John Harrison
2022-11-29 21:12 ` [Intel-gfx] [PATCH 2/2] drm/i915/guc: Look for a guilty context when an engine reset fails John.C.Harrison
2022-11-30 8:30 ` Tvrtko Ursulin
2022-11-30 21:04 ` John Harrison
2022-12-01 10:21 ` Tvrtko Ursulin
2022-12-13 2:00 ` Umesh Nerlige Ramappa
2022-11-30 0:08 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Allow error capture without a request / on reset failure Patchwork
2022-11-30 1:27 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
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=20221129211253.3183480-1-John.C.Harrison@Intel.com \
--to=john.c.harrison@intel.com \
--cc=DRI-Devel@Lists.FreeDesktop.Org \
--cc=Intel-GFX@Lists.FreeDesktop.Org \
/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