From: John.C.Harrison@Intel.com
To: Intel-GFX@Lists.FreeDesktop.Org
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: [Intel-gfx] [PATCH v2 0/2] Improvements to GuC load failure handling
Date: Thu, 16 Mar 2023 15:06:30 -0700 [thread overview]
Message-ID: <20230316220632.3312218-1-John.C.Harrison@Intel.com> (raw)
From: John Harrison <John.C.Harrison@Intel.com>
Add more decoding of the GuC load failures. Also include information
about GT frequency to see if timeouts are due to a failure to boost
the clocks. Finally, increase the timeout to accommodate situations
where the clock boost does fail.
v2: Reduce timeout in release builds, add bug references, make usage
of 'success' variable a litte clearer (review feedback from Daniele).
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
John Harrison (2):
drm/i915/guc: Improve GuC load error reporting
drm/i915/guc: Allow for very slow GuC loading
.../gpu/drm/i915/gt/uc/abi/guc_errors_abi.h | 17 +++
drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c | 141 +++++++++++++++---
drivers/gpu/drm/i915/gt/uc/intel_guc_reg.h | 4 +-
3 files changed, 140 insertions(+), 22 deletions(-)
--
2.39.1
next reply other threads:[~2023-03-16 22:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 22:06 John.C.Harrison [this message]
2023-03-16 22:06 ` [Intel-gfx] [PATCH v2 1/2] drm/i915/guc: Improve GuC load error reporting John.C.Harrison
2023-03-16 22:06 ` [Intel-gfx] [PATCH v2 2/2] drm/i915/guc: Allow for very slow GuC loading John.C.Harrison
2023-03-17 22:33 ` Dixit, Ashutosh
2023-03-22 21:14 ` Ceraolo Spurio, Daniele
2023-03-23 2:40 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Improvements to GuC load failure handling (rev3) Patchwork
2023-03-23 22:30 ` John Harrison
2023-03-23 2:40 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-03-23 2:52 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-03-23 22:29 ` John Harrison
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=20230316220632.3312218-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