From: Matthew Brost <matthew.brost@intel.com>
To: <gfx-internal-devel@eclists.intel.com>,
<dri-devel@lists.freedesktop.org>
Subject: [PATCH 0/9] Clean up some CI failures for GuC submission
Date: Wed, 11 Aug 2021 01:16:13 +0000 [thread overview]
Message-ID: <20210811011622.255784-1-matthew.brost@intel.com> (raw)
Resets are notoriously hard to get fully working and notoriously racey,
especially with selftests / IGTs that do all sorts of wild things that
would be near impossible to hit during normal use cases. Even though
likely impossible to hit, anything selftests / IGTs uncover needs to be
fixed. This series addresses 7 such issues, adds a workaround to a
selftest, and add another selftest to prove scrubbing of G2H during a
reset works.
v2:
(Daniel Vetter)
- Split fixes into individual patches
- A kernel doc
- A VLK ref for selftest workaround
(Checkpatch)
- Fix warnings
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Matthew Brost (9):
drm/i915/guc: Fix blocked context accounting
drm/i915/guc: outstanding G2H accounting
drm/i915/guc: Unwind context requests in reverse order
drm/i915/guc: Don't drop ce->guc_active.lock when unwinding context
drm/i915/guc: Flush the work queue for GuC generated G2H
drm/i915/guc: Do not clear enable during reset in an enable is
inflight
drm/i915/guc: Don't enable scheduling on a banned context
drm/i915/selftests: Fix memory corruption in live_lrc_isolation
drm/i915/selftests: Add initial GuC selftest for scrubbing lost G2H
drivers/gpu/drm/i915/gt/intel_context_types.h | 18 +++
drivers/gpu/drm/i915/gt/selftest_lrc.c | 29 +++-
.../gpu/drm/i915/gt/uc/intel_guc_submission.c | 69 +++++++---
drivers/gpu/drm/i915/gt/uc/selftest_guc.c | 126 ++++++++++++++++++
.../drm/i915/selftests/i915_live_selftests.h | 1 +
.../i915/selftests/intel_scheduler_helpers.c | 12 ++
.../i915/selftests/intel_scheduler_helpers.h | 2 +
7 files changed, 239 insertions(+), 18 deletions(-)
create mode 100644 drivers/gpu/drm/i915/gt/uc/selftest_guc.c
--
2.32.0
next reply other threads:[~2021-08-11 1:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 1:16 Matthew Brost [this message]
2021-08-11 1:16 ` [PATCH 1/9] drm/i915/guc: Fix blocked context accounting Matthew Brost
2021-08-11 10:30 ` Daniel Vetter
2021-08-11 17:28 ` Matthew Brost
2021-08-11 1:16 ` [PATCH 2/9] drm/i915/guc: outstanding G2H accounting Matthew Brost
2021-08-11 1:16 ` [PATCH 3/9] drm/i915/guc: Unwind context requests in reverse order Matthew Brost
2021-08-11 1:16 ` [PATCH 4/9] drm/i915/guc: Don't drop ce->guc_active.lock when unwinding context Matthew Brost
2021-08-11 1:16 ` [PATCH 5/9] drm/i915/guc: Flush the work queue for GuC generated G2H Matthew Brost
2021-08-12 14:11 ` Daniel Vetter
2021-08-12 15:23 ` Matthew Brost
2021-08-12 19:47 ` Daniel Vetter
2021-08-12 22:38 ` Matthew Brost
2021-08-13 15:11 ` Daniel Vetter
2021-08-13 19:02 ` Matthew Brost
2021-08-16 15:39 ` Daniel Vetter
2021-08-11 1:16 ` [PATCH 6/9] drm/i915/guc: Do not clear enable during reset in an enable is inflight Matthew Brost
2021-08-11 1:16 ` [PATCH 7/9] drm/i915/guc: Don't enable scheduling on a banned context Matthew Brost
2021-08-11 1:16 ` [PATCH 8/9] drm/i915/selftests: Fix memory corruption in live_lrc_isolation Matthew Brost
2021-08-11 1:16 ` [PATCH 9/9] drm/i915/selftests: Add initial GuC selftest for scrubbing lost G2H 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=20210811011622.255784-1-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gfx-internal-devel@eclists.intel.com \
/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