From: Matthew Brost <matthew.brost@intel.com>
To: <intel-gfx@lists.freedesktop.org>, <dri-devel@lists.freedesktop.org>
Cc: <daniele.ceraolospurio@intel.com>, <john.c.harrison@intel.com>
Subject: [Intel-gfx] [PATCH 0/4] Do error capture async, flush G2H processing on reset
Date: Mon, 13 Sep 2021 22:09:52 -0700 [thread overview]
Message-ID: <20210914050956.30685-1-matthew.brost@intel.com> (raw)
Rather allocating an error capture in nowait context to break a lockdep
splat [1], do the error capture async compared to the G2H processing.
v2: Fix Docs warning
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
[1] https://patchwork.freedesktop.org/patch/451415/?series=93704&rev=5
John Harrison (1):
drm/i915/guc: Refcount context during error capture
Matthew Brost (3):
drm/i915/guc: Move guc_ids under submission_state sub-structure
drm/i915/guc: Do error capture asynchronously
drm/i915/guc: Flush G2H work queue during reset
drivers/gpu/drm/i915/gt/intel_context.c | 2 +
drivers/gpu/drm/i915/gt/intel_context_types.h | 16 ++-
drivers/gpu/drm/i915/gt/uc/intel_guc.h | 36 +++--
.../gpu/drm/i915/gt/uc/intel_guc_submission.c | 133 ++++++++++++------
4 files changed, 130 insertions(+), 57 deletions(-)
--
2.32.0
next reply other threads:[~2021-09-14 5:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 5:09 Matthew Brost [this message]
2021-09-14 5:09 ` [Intel-gfx] [PATCH 1/4] drm/i915/guc: Move guc_ids under submission_state sub-structure Matthew Brost
2021-09-14 5:09 ` [Intel-gfx] [PATCH 2/4] drm/i915/guc: Do error capture asynchronously Matthew Brost
2021-09-14 14:25 ` Daniel Vetter
2021-09-15 0:04 ` Matthew Brost
2021-09-14 5:09 ` [Intel-gfx] [PATCH 3/4] drm/i915/guc: Flush G2H work queue during reset Matthew Brost
2021-09-14 5:09 ` [Intel-gfx] [PATCH 4/4] drm/i915/guc: Refcount context during error capture Matthew Brost
2021-09-14 14:29 ` Daniel Vetter
2021-09-14 23:23 ` John Harrison
2021-09-17 12:37 ` Daniel Vetter
2021-09-14 23:36 ` Matthew Brost
2021-09-17 12:40 ` Daniel Vetter
2021-09-14 6:06 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Do error capture async, flush G2H processing on reset (rev2) Patchwork
2021-09-14 6:36 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-09-14 16:28 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Do error capture async, flush G2H processing on reset (rev3) Patchwork
2021-09-14 16:53 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2021-09-14 4:24 [Intel-gfx] [PATCH 0/4] Do error capture async, flush G2H processing on reset 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=20210914050956.30685-1-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=john.c.harrison@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