From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/4] drm/i915: Include interesting seqno in the missed breadcrumb debug
Date: Mon, 24 Apr 2017 15:52:25 +0300 [thread overview]
Message-ID: <877f2a2cja.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20170423170619.7156-4-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Knowing the neighbouring seqno (current on hw, last submitted to hw)
> provide some useful breadcrumbs to the debug log.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Mika Kuoppala <mika.kuoppala@intel.com>
> ---
> drivers/gpu/drm/i915/intel_breadcrumbs.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_breadcrumbs.c b/drivers/gpu/drm/i915/intel_breadcrumbs.c
> index 9ccbf26124c6..35da5928bd8a 100644
> --- a/drivers/gpu/drm/i915/intel_breadcrumbs.c
> +++ b/drivers/gpu/drm/i915/intel_breadcrumbs.c
> @@ -64,10 +64,12 @@ static unsigned long wait_timeout(void)
>
> static noinline void missed_breadcrumb(struct intel_engine_cs *engine)
> {
> - DRM_DEBUG_DRIVER("%s missed breadcrumb at %pF, irq posted? %s\n",
> + DRM_DEBUG_DRIVER("%s missed breadcrumb at %pF, irq posted? %s, current seqno=%x, last=%x\n",
> engine->name, __builtin_return_address(0),
> yesno(test_bit(ENGINE_IRQ_BREADCRUMB,
> - &engine->irq_posted)));
> + &engine->irq_posted)),
> + intel_engine_get_seqno(engine),
> + intel_engine_last_submit(engine));
>
> set_bit(engine->id, &engine->i915->gpu_error.missed_irq_rings);
> }
> --
> 2.11.0
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-04-24 12:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-23 17:06 [PATCH 1/4] drm/i915: Differentiate between sw write location into ring and last hw read Chris Wilson
2017-04-23 17:06 ` [PATCH 2/4] drm/i915: Poison the request before emitting commands Chris Wilson
2017-04-24 12:29 ` Mika Kuoppala
2017-04-24 12:50 ` Chris Wilson
2017-04-23 17:06 ` [PATCH 3/4] drm/i915: Compute the ring->space slightly less pessimistically Chris Wilson
2017-04-24 12:37 ` Mika Kuoppala
2017-04-24 12:52 ` Chris Wilson
2017-04-23 17:06 ` [PATCH 4/4] drm/i915: Include interesting seqno in the missed breadcrumb debug Chris Wilson
2017-04-24 12:52 ` Mika Kuoppala [this message]
2017-04-24 14:56 ` Chris Wilson
2017-04-23 17:24 ` ✓ Fi.CI.BAT: success for series starting with [1/4] drm/i915: Differentiate between sw write location into ring and last hw read Patchwork
2017-04-23 17:52 ` [PATCH 1/4] " Chris Wilson
2017-04-24 12:21 ` Mika Kuoppala
2017-04-24 12:32 ` Chris Wilson
2017-04-24 12:41 ` Chris Wilson
2017-04-25 13:00 ` [PATCH v2] " Chris Wilson
2017-04-25 13:50 ` Mika Kuoppala
2017-04-25 14:44 ` Chris Wilson
2017-04-25 13:19 ` ✓ Fi.CI.BAT: success for series starting with [v2] drm/i915: Differentiate between sw write location into ring and last hw read (rev2) 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=877f2a2cja.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=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.