From: John.C.Harrison@Intel.com
To: Intel-GFX@Lists.FreeDesktop.Org
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: [Intel-gfx] [PATCH 0/3] Update to GuC v70
Date: Fri, 8 Apr 2022 11:03:23 -0700 [thread overview]
Message-ID: <20220408180326.1454951-1-John.C.Harrison@Intel.com> (raw)
From: John Harrison <John.C.Harrison@Intel.com>
Update to the latest GuC firmware release.
Note that this includes some significant backwards breaking API
changes. One is about context registration - the descriptor pool is
gone, all parameters are passed via the CTB instead. The second is
about scheduling policy updates - they are now done via a single KLV
based H2G instead of multiple direct H2Gs. The patches to implement
these two changes are being sent split initially for ease of review.
However, for final merge, they will need to be squashed into a single
atomic commit.
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
John Harrison (3):
drm/i915/guc: Update context registration to new GuC API
drm/i915/guc: Update scheduling policies to new GuC API
drm/i915/guc: Update to GuC version 70.1.1
.../gpu/drm/i915/gt/uc/abi/guc_actions_abi.h | 4 +-
drivers/gpu/drm/i915/gt/uc/abi/guc_klvs_abi.h | 15 +
drivers/gpu/drm/i915/gt/uc/intel_guc.h | 5 -
drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h | 67 ++--
.../gpu/drm/i915/gt/uc/intel_guc_submission.c | 375 +++++++++++-------
drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 32 +-
6 files changed, 294 insertions(+), 204 deletions(-)
--
2.25.1
next reply other threads:[~2022-04-08 18:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 18:03 John.C.Harrison [this message]
2022-04-08 18:03 ` [Intel-gfx] [PATCH 1/3] drm/i915/guc: Update context registration to new GuC API John.C.Harrison
2022-04-12 0:13 ` Ceraolo Spurio, Daniele
2022-04-08 18:03 ` [Intel-gfx] [PATCH 2/3] drm/i915/guc: Update scheduling policies " John.C.Harrison
2022-04-12 0:35 ` Ceraolo Spurio, Daniele
2022-04-08 18:03 ` [Intel-gfx] [PATCH 3/3] drm/i915/guc: Update to GuC version 70.1.1 John.C.Harrison
2022-04-12 0:36 ` Ceraolo Spurio, Daniele
2022-04-08 21:44 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Update to GuC v70 Patchwork
2022-04-08 21:45 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-04-08 22:20 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-09 0:15 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20220408180326.1454951-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