From: John.C.Harrison@Intel.com
To: Intel-GFX@Lists.FreeDesktop.Org
Cc: John Harrison <John.C.Harrison@Intel.com>,
DRI-Devel@Lists.FreeDesktop.Org
Subject: [PATCH 0/8] Prep work for next GuC release
Date: Thu, 17 Feb 2022 15:51:59 -0800 [thread overview]
Message-ID: <20220217235207.930153-1-John.C.Harrison@Intel.com> (raw)
From: John Harrison <John.C.Harrison@Intel.com>
The next GuC firmware release includes some significant backwards
breaking API changes. One such is that there is no longer an LRC
descriptor pool. A bunch of prep work for that change can be done in
advance - the descriptor pool was being used for things it shouldn't
really have been used for anyway.
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
John Harrison (8):
drm/i915/guc: Do not conflate lrc_desc with GuC id for registration
drm/i915/guc: Add an explicit 'submission_initialized' flag
drm/i915/guc: Better name for context id limit
drm/i915/guc: Split guc_lrc_desc_pin apart
drm/i915/guc: Move lrc desc setup to where it is needed
drm/i915/guc: Rename desc_idx to ctx_id
drm/i915/guc: Drop obsolete H2G definitions
drm/i915/guc: Fix potential invalid pointer dereferences when decoding
G2Hs
drivers/gpu/drm/i915/gt/intel_context.c | 2 +-
.../gpu/drm/i915/gt/uc/abi/guc_actions_abi.h | 2 -
drivers/gpu/drm/i915/gt/uc/intel_guc.h | 2 +
drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h | 4 +-
.../gpu/drm/i915/gt/uc/intel_guc_submission.c | 183 ++++++++++--------
drivers/gpu/drm/i915/gt/uc/selftest_guc.c | 2 +-
6 files changed, 112 insertions(+), 83 deletions(-)
--
2.25.1
next reply other threads:[~2022-02-17 23:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 23:51 John.C.Harrison [this message]
2022-02-17 23:52 ` [PATCH 1/8] drm/i915/guc: Do not conflate lrc_desc with GuC id for registration John.C.Harrison
2022-02-18 21:13 ` Ceraolo Spurio, Daniele
2022-02-17 23:52 ` [PATCH 2/8] drm/i915/guc: Add an explicit 'submission_initialized' flag John.C.Harrison
2022-02-18 21:18 ` [Intel-gfx] " Ceraolo Spurio, Daniele
2022-02-17 23:52 ` [PATCH 3/8] drm/i915/guc: Better name for context id limit John.C.Harrison
2022-02-23 1:00 ` Ceraolo Spurio, Daniele
2022-02-17 23:52 ` [PATCH 4/8] drm/i915/guc: Split guc_lrc_desc_pin apart John.C.Harrison
2022-02-23 1:04 ` [Intel-gfx] " Ceraolo Spurio, Daniele
2022-02-17 23:52 ` [PATCH 5/8] drm/i915/guc: Move lrc desc setup to where it is needed John.C.Harrison
2022-02-23 1:12 ` [Intel-gfx] " Ceraolo Spurio, Daniele
2022-02-23 20:23 ` John Harrison
2022-02-24 2:03 ` Ceraolo Spurio, Daniele
2022-02-24 21:13 ` John Harrison
2022-02-17 23:52 ` [PATCH 6/8] drm/i915/guc: Rename desc_idx to ctx_id John.C.Harrison
2022-02-23 1:14 ` Ceraolo Spurio, Daniele
2022-02-17 23:52 ` [PATCH 7/8] drm/i915/guc: Drop obsolete H2G definitions John.C.Harrison
2022-02-23 1:19 ` Ceraolo Spurio, Daniele
2022-02-17 23:52 ` [PATCH 8/8] drm/i915/guc: Fix potential invalid pointer dereferences when decoding G2Hs John.C.Harrison
2022-02-23 1:28 ` Ceraolo Spurio, Daniele
-- strict thread matches above, loose matches on Subject: below --
2022-02-08 2:20 [PATCH 0/8] Prep work for next GuC release 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=20220217235207.930153-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