From: John.C.Harrison@Intel.com
To: Intel-GFX@Lists.FreeDesktop.Org
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: [Intel-gfx] [PATCH 0/4] Assorted fixes/tweaks to GuC support
Date: Thu, 2 Dec 2021 16:06:19 -0800 [thread overview]
Message-ID: <20211203000623.3086309-1-John.C.Harrison@Intel.com> (raw)
From: John Harrison <John.C.Harrison@Intel.com>
Fix a potential null pointer dereference, improve debug crash reports,
improve code separation, improve GuC/HuC load performance.
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
John Harrison (3):
drm/i915/uc: Allow platforms to have GuC but not HuC
drm/i915/guc: Increase GuC log size for CONFIG_DEBUG_GEM
drm/i915/guc: Don't go bang in GuC log if no GuC
Vinay Belgaumkar (1):
drm/i915/guc: Request RP0 before loading firmware
drivers/gpu/drm/i915/gt/intel_rps.c | 59 ++++++++++++
drivers/gpu/drm/i915/gt/intel_rps.h | 2 +
drivers/gpu/drm/i915/gt/uc/intel_guc_log.h | 5 +-
.../drm/i915/gt/uc/intel_guc_log_debugfs.c | 4 +-
drivers/gpu/drm/i915/gt/uc/intel_uc.c | 6 ++
drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 93 +++++++++++++------
drivers/gpu/drm/i915/i915_reg.h | 4 +
7 files changed, 140 insertions(+), 33 deletions(-)
--
2.25.1
next reply other threads:[~2021-12-03 0:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 0:06 John.C.Harrison [this message]
2021-12-03 0:06 ` [Intel-gfx] [PATCH 1/4] drm/i915/uc: Allow platforms to have GuC but not HuC John.C.Harrison
2021-12-03 0:06 ` [Intel-gfx] [PATCH 2/4] drm/i915/guc: Request RP0 before loading firmware John.C.Harrison
2021-12-03 0:06 ` [Intel-gfx] [PATCH 3/4] drm/i915/guc: Increase GuC log size for CONFIG_DEBUG_GEM John.C.Harrison
2021-12-03 0:06 ` [Intel-gfx] [PATCH 4/4] drm/i915/guc: Don't go bang in GuC log if no GuC John.C.Harrison
2021-12-03 0:33 ` Lucas De Marchi
2021-12-03 20:00 ` Daniele Ceraolo Spurio
2021-12-07 7:01 ` Lucas De Marchi
2021-12-03 0:20 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Assorted fixes/tweaks to GuC support Patchwork
2021-12-03 0:21 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-12-03 0:44 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-12-03 1:55 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-12-04 1:23 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Assorted fixes/tweaks to GuC support (rev3) Patchwork
2021-12-04 1:24 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-12-04 2:03 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2021-12-10 4:40 [Intel-gfx] [PATCH 0/4] Assorted fixes/tweaks to GuC support John.C.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=20211203000623.3086309-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