From: Arun Siluvery <arun.siluvery@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/5] Capture more useful details in error state
Date: Thu, 28 Jan 2016 19:01:19 +0000 [thread overview]
Message-ID: <1454007684-16777-1-git-send-email-arun.siluvery@linux.intel.com> (raw)
Few patches to capture more useful details in error state - these details
include execlist state, csb events and their decoded form, WA ctx batch
buffer.
Except WA ctx batch all other patches are already sent as part of preemption
patch series but these are independent patches; it may take a while before
preemption patches are reviewed, merged but these patches can be useful now so
extracted them from that series.
Example output looks like this,
EXECLIST_STATUS: 0x00000301
EXECLIST_CTX_ID: 0x00000000
EXECLIST_CSBPTR: 0x00000505
EXECLIST_CSB_WR: 5
EXECLIST_CSB_RD: 5
EXECLIST_SWL_RD: 5
EXECLIST_CTX/CSB[0]: 0x000.00000 / 0x00000001 | I->A | | | | | |
EXECLIST_CTX/CSB[1]: 0x000.00a33 / 0x00000018 | | | | A->I | DONE | |
EXECLIST_CTX/CSB[2]: 0x000.00000 / 0x00000001 | I->A | | | | | |
EXECLIST_CTX/CSB[3]: 0x000.00a33 / 0x00000018 | | | | A->I | DONE | |
EXECLIST_CTX/CSB[4]: 0x000.00000 / 0x00000001 | I->A | | | | | |
EXECLIST_CTX/CSB[5]: 0x000.00a33 / 0x00000018 | | | | A->I | DONE | |
Arun Siluvery (1):
drm/i915/error: Capture WA ctx batch in error state
Dave Gordon (4):
drm/i915/error: capture execlist state on error
drm/i915/error: capture ringbuffer pointed to by START
drm/i915/error: report ctx id & desc for each request in the queue
drm/i915/error: improve CSB reporting
drivers/gpu/drm/i915/i915_drv.h | 14 ++-
drivers/gpu/drm/i915/i915_gpu_error.c | 175 +++++++++++++++++++++++++++++-----
2 files changed, 165 insertions(+), 24 deletions(-)
--
1.9.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2016-01-28 19:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 19:01 Arun Siluvery [this message]
2016-01-28 19:01 ` [PATCH 1/5] drm/i915/error: capture execlist state on error Arun Siluvery
2016-01-29 7:49 ` Mika Kuoppala
2016-01-29 11:45 ` Chris Wilson
2016-01-29 12:25 ` Arun Siluvery
2016-01-29 12:38 ` Chris Wilson
2016-01-28 19:01 ` [PATCH 2/5] drm/i915/error: capture ringbuffer pointed to by START Arun Siluvery
2016-01-29 11:47 ` Chris Wilson
2016-02-01 21:30 ` Arun Siluvery
2016-01-28 19:01 ` [PATCH 3/5] drm/i915/error: report ctx id & desc for each request in the queue Arun Siluvery
2016-01-29 8:17 ` Mika Kuoppala
2016-01-29 9:48 ` Arun Siluvery
2016-01-28 19:01 ` [PATCH 4/5] drm/i915/error: improve CSB reporting Arun Siluvery
2016-01-28 19:01 ` [PATCH 5/5] drm/i915/error: Capture WA ctx batch in error state Arun Siluvery
2016-01-29 7:52 ` Mika Kuoppala
2016-01-29 10:09 ` Arun Siluvery
2016-01-29 10:59 ` ✗ Fi.CI.BAT: failure for Capture more useful details " Patchwork
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=1454007684-16777-1-git-send-email-arun.siluvery@linux.intel.com \
--to=arun.siluvery@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).