All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/i915: Show IPEIR and IPEHR in the engine dump
Date: Mon, 18 Dec 2017 11:14:35 +0000	[thread overview]
Message-ID: <151359567537.29397.9083721026446750275@mail.alporthouse.com> (raw)
In-Reply-To: <20171217132852.30642-2-chris@chris-wilson.co.uk>

Quoting Chris Wilson (2017-12-17 13:28:51)
> A useful bit of information for inspecting GPU stalls from
> intel_engine_dump() are the error registers, IPEIR and IPEHR.
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> ---
>  drivers/gpu/drm/i915/intel_engine_cs.c | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/intel_engine_cs.c b/drivers/gpu/drm/i915/intel_engine_cs.c
> index 510e0bc3a377..05bd9e17452c 100644
> --- a/drivers/gpu/drm/i915/intel_engine_cs.c
> +++ b/drivers/gpu/drm/i915/intel_engine_cs.c
> @@ -1757,6 +1757,13 @@ void intel_engine_dump(struct intel_engine_cs *engine,
>         addr = intel_engine_get_last_batch_head(engine);
>         drm_printf(m, "    BBADDR: 0x%08x_%08x\n",
>                    upper_32_bits(addr), lower_32_bits(addr));
> +       addr = I915_READ(RING_DMA_FADD(engine->mmio_base));

if (GEN >= 8)
	addr |= (u64)I915_READ(RING_DMA_FADD_UDW) << 32;
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2017-12-18 11:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-17 13:28 [PATCH 1/3] drm/i915: Re-enable GGTT earlier after GPU reset Chris Wilson
2017-12-17 13:28 ` [PATCH 2/3] drm/i915: Show IPEIR and IPEHR in the engine dump Chris Wilson
2017-12-18 11:14   ` Tvrtko Ursulin
2017-12-18 11:18     ` Chris Wilson
2017-12-18 11:14   ` Chris Wilson [this message]
2017-12-18 11:26   ` [PATCH v2] " Chris Wilson
2017-12-18 12:08     ` Tvrtko Ursulin
2017-12-18 12:17   ` [PATCH v3] " Chris Wilson
2017-12-18 12:32     ` Tvrtko Ursulin
2017-12-18 12:35       ` Chris Wilson
2017-12-18 12:39   ` [PATCH v4] " Chris Wilson
2017-12-18 12:58     ` Tvrtko Ursulin
2017-12-18 13:27       ` Chris Wilson
2017-12-17 13:28 ` [PATCH 3/3] drm/i915/selftests: Fix up igt_reset_engine Chris Wilson
2017-12-18 21:50   ` Michel Thierry
2017-12-18 21:54     ` Chris Wilson
2017-12-17 14:07 ` ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915: Re-enable GGTT earlier after GPU reset Patchwork
2017-12-17 15:36 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-12-17 18:19 ` [PATCH 1/3] " Chris Wilson
2017-12-18 11:11 ` Tvrtko Ursulin
2017-12-18 11:19   ` Chris Wilson
2017-12-18 13:13 ` ✗ Fi.CI.BAT: failure for series starting with [1/3] drm/i915: Re-enable GGTT earlier after GPU reset (rev4) 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=151359567537.29397.9083721026446750275@mail.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --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.