From: Matthew Brost <matthew.brost@intel.com>
To: <intel-gfx@lists.freedesktop.org>, <dri-devel@lists.freedesktop.org>
Subject: [Intel-gfx] [PATCH 0/7] Fix stealing guc_ids + test
Date: Fri, 10 Dec 2021 16:56:05 -0800 [thread overview]
Message-ID: <20211211005612.8575-1-matthew.brost@intel.com> (raw)
Patches 1 & 2 address bugs in stealing of guc_ids and patch 7 tests this
path.
Patches 4-6 address some issues with the CTs exposed by the selftest in
patch 7. Basically if a lot of contexts were all deregistered all at
once, the CT channel could deadlock.
Patch 3 is a small fix that is already review but just included for CI.
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
John Harrison (1):
drm/i915/guc: Don't hog IRQs when destroying contexts
Matthew Brost (6):
drm/i915/guc: Use correct context lock when callig
clr_context_registered
drm/i915/guc: Only assign guc_id.id when stealing guc_id
drm/i915/guc: Remove racey GEM_BUG_ON
drm/i915/guc: Add extra debug on CT deadlock
drm/i915/guc: Kick G2H tasklet if no credits
drm/i915/guc: Selftest for stealing of guc ids
drivers/gpu/drm/i915/gt/uc/intel_guc.h | 12 ++
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 18 +-
.../gpu/drm/i915/gt/uc/intel_guc_submission.c | 68 ++++---
drivers/gpu/drm/i915/gt/uc/selftest_guc.c | 171 ++++++++++++++++++
4 files changed, 241 insertions(+), 28 deletions(-)
--
2.33.1
next reply other threads:[~2021-12-11 1:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 0:56 Matthew Brost [this message]
2021-12-11 0:56 ` [Intel-gfx] [PATCH 1/7] drm/i915/guc: Use correct context lock when callig clr_context_registered Matthew Brost
2021-12-11 0:56 ` [Intel-gfx] [PATCH 2/7] drm/i915/guc: Only assign guc_id.id when stealing guc_id Matthew Brost
2021-12-11 1:08 ` John Harrison
2021-12-11 0:56 ` [Intel-gfx] [PATCH 3/7] drm/i915/guc: Remove racey GEM_BUG_ON Matthew Brost
2021-12-11 0:56 ` [Intel-gfx] [PATCH 4/7] drm/i915/guc: Don't hog IRQs when destroying contexts Matthew Brost
2021-12-11 1:07 ` John Harrison
2021-12-11 1:10 ` Matthew Brost
2021-12-11 0:56 ` [Intel-gfx] [PATCH 5/7] drm/i915/guc: Add extra debug on CT deadlock Matthew Brost
2021-12-11 1:43 ` John Harrison
2021-12-11 1:45 ` John Harrison
2021-12-11 3:24 ` Matthew Brost
2021-12-11 0:56 ` [Intel-gfx] [PATCH 6/7] drm/i915/guc: Kick G2H tasklet if no credits Matthew Brost
2021-12-11 0:56 ` [Intel-gfx] [PATCH 7/7] drm/i915/guc: Selftest for stealing of guc ids Matthew Brost
2021-12-11 1:33 ` John Harrison
2021-12-11 3:31 ` Matthew Brost
2021-12-11 3:32 ` Matthew Brost
2021-12-11 2:28 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix stealing guc_ids + test Patchwork
2021-12-11 2:30 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-12-11 2:58 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-12-12 1:32 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2021-12-11 17:35 [Intel-gfx] [PATCH 0/7] " Matthew Brost
2021-12-14 17:04 Matthew Brost
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=20211211005612.8575-1-matthew.brost@intel.com \
--to=matthew.brost@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