From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH 6/6] drm/i915: collect more per ring error state
Date: Tue, 11 Oct 2011 17:01:24 +0100 [thread overview]
Message-ID: <c55c5d$o2it2@AZSMGA002.ch.intel.com> (raw)
In-Reply-To: <1318343954-14607-6-git-send-email-daniel.vetter@ffwll.ch>
On Tue, 11 Oct 2011 16:39:14 +0200, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> Based on a patch by Ben Widawsky, but with different colors
> for the bikeshed.
>
> In contrast to Ben's patch this one doesn't add the fault regs.
> Afaics they're for the optional page fault support which
> - we're not enabling
> - and which seems to be unsupported by the hw team. Recent bspec
> lacks tons of information about this that the public docs released
> half a year back still contain.
>
> Also dump ring HEAD/TAIL registers - I've recently seen a few
> error_state where just guessing these is not good enough.
>
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> dump head/tail into error_state
> ---
> drivers/gpu/drm/i915/i915_debugfs.c | 5 ++++-
> drivers/gpu/drm/i915/i915_drv.h | 5 ++++-
> drivers/gpu/drm/i915/i915_irq.c | 7 ++++++-
> drivers/gpu/drm/i915/i915_reg.h | 2 ++
> 4 files changed, 16 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> index ea7237d..5d73ae5 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -733,17 +733,20 @@ static void i915_ring_error_state(struct seq_file *m,
> unsigned ring)
> {
> seq_printf(m, "%s command stream:\n", ring_str(ring));
> + seq_printf(m, " HEAD: 0x%08x\n", error->head[ring]);
> + seq_printf(m, " TAIL: 0x%08x\n", error->tail[ring]);
> seq_printf(m, " ACTHD: 0x%08x\n", error->acthd[ring]);
> seq_printf(m, " IPEIR: 0x%08x\n", error->ipeir[ring]);
> seq_printf(m, " IPEHR: 0x%08x\n", error->ipehr[ring]);
> seq_printf(m, " INSTDONE: 0x%08x\n", error->instdone[ring]);
> + seq_printf(m, " INSTPS: 0x%08x\n", error->instps[ring]);
> if (ring == RCS) {
> if (INTEL_INFO(dev)->gen >= 4) {
> seq_printf(m, " INSTDONE1: 0x%08x\n", error->instdone1);
> - seq_printf(m, " INSTPS: 0x%08x\n", error->instps);
> }
> seq_printf(m, " INSTPM: 0x%08x\n", error->instpm);
Hmm, isn't INSTPM also per-ring?
Can you also add the DMA fetch addresses whilst you are here? I've never
found an instance where they were more informative than the ACTHD, but
that was only for a very small sampling of local errors.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-10-11 16:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 14:39 [PATCH 1/6] drm/i915: hangcheck robustification Daniel Vetter
2011-10-11 14:39 ` [PATCH 2/6] drm/i915: kicking rings stuck on semaphores considered harmful Daniel Vetter
2011-10-11 15:51 ` Chris Wilson
2011-10-11 20:48 ` Ben Widawsky
2011-10-11 14:39 ` [PATCH 3/6] drm/i915: don't bail out of intel_wait_ring_buffer too early Daniel Vetter
2011-10-11 15:53 ` Chris Wilson
2011-10-11 17:25 ` [PATCH] " Daniel Vetter
2011-10-18 15:24 ` Chris Wilson
2011-10-11 14:39 ` [PATCH 4/6] drm/i915: switch ring->id to be a real id Daniel Vetter
2011-10-11 15:55 ` Chris Wilson
2011-10-11 17:27 ` [PATCH] drm/i915: don't bail out of intel_wait_ring_buffer too early Daniel Vetter
2011-10-11 19:31 ` Daniel Vetter
2011-10-11 17:29 ` [PATCH] drm/i915: switch ring->id to be a real id Daniel Vetter
2011-10-18 15:27 ` Chris Wilson
2011-10-11 14:39 ` [PATCH 5/6] drm/i915: refactor ring error state capture to use arrays Daniel Vetter
2011-10-11 15:57 ` Chris Wilson
2011-10-11 14:39 ` [PATCH 6/6] drm/i915: collect more per ring error state Daniel Vetter
2011-10-11 16:01 ` Chris Wilson [this message]
2011-10-11 17:30 ` [PATCH] " Daniel Vetter
2011-10-11 19:23 ` Chris Wilson
2011-10-11 19:20 ` Daniel Vetter
2011-10-30 18:39 ` Chris Wilson
2011-10-30 18:46 ` Chris Wilson
2011-10-19 11:32 ` [PATCH 1/6] drm/i915: hangcheck robustification Chris Wilson
2011-10-19 15:02 ` Ben Widawsky
2011-10-19 15:48 ` Chris Wilson
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='c55c5d$o2it2@AZSMGA002.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--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 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.