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: [PATCH 0/3] Do error capture async, flush G2H processing on reset
Date: Thu, 21 Oct 2021 18:29:36 -0700 [thread overview]
Message-ID: <20211022012939.22363-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
v3: Rebase, resend for CI
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
[1] https://patchwork.freedesktop.org/patch/451415/?series=93704&rev=5
Matthew Brost (2):
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 | 7 ++
drivers/gpu/drm/i915/gt/uc/intel_guc.h | 10 ++
.../gpu/drm/i915/gt/uc/intel_guc_submission.c | 97 ++++++++++++++-----
4 files changed, 91 insertions(+), 25 deletions(-)
--
2.32.0
WARNING: multiple messages have this Message-ID (diff)
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/3] Do error capture async, flush G2H processing on reset
Date: Thu, 21 Oct 2021 18:29:36 -0700 [thread overview]
Message-ID: <20211022012939.22363-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
v3: Rebase, resend for CI
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
[1] https://patchwork.freedesktop.org/patch/451415/?series=93704&rev=5
Matthew Brost (2):
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 | 7 ++
drivers/gpu/drm/i915/gt/uc/intel_guc.h | 10 ++
.../gpu/drm/i915/gt/uc/intel_guc_submission.c | 97 ++++++++++++++-----
4 files changed, 91 insertions(+), 25 deletions(-)
--
2.32.0
next reply other threads:[~2021-10-22 1:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 1:29 Matthew Brost [this message]
2021-10-22 1:29 ` [Intel-gfx] [PATCH 0/3] Do error capture async, flush G2H processing on reset Matthew Brost
2021-10-22 1:29 ` [PATCH 1/3] drm/i915/guc: Do error capture asynchronously Matthew Brost
2021-10-22 1:29 ` [Intel-gfx] " Matthew Brost
2021-10-22 1:29 ` [PATCH 2/3] drm/i915/guc: Flush G2H work queue during reset Matthew Brost
2021-10-22 1:29 ` [Intel-gfx] " Matthew Brost
2021-10-22 1:29 ` [PATCH 3/3] drm/i915/guc: Refcount context during error capture Matthew Brost
2021-10-22 1:29 ` [Intel-gfx] " Matthew Brost
2021-10-22 3:24 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Do error capture async, flush G2H processing on reset (rev4) Patchwork
2021-10-22 3:53 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-10-23 0:39 [PATCH 0/3] Do error capture async, flush G2H processing on reset Matthew Brost
2021-10-23 18:05 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=20211022012939.22363-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.