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/6] drm/i915: Include ring->emit in debugging
Date: Fri, 09 Mar 2018 15:41:32 +0200 [thread overview]
Message-ID: <87zi3hmkmr.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20180307134226.25492-4-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Include ring->emit and ring->space alongside ring->(head,tail) when
> printing debug information.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/i915_debugfs.c | 4 ++--
> drivers/gpu/drm/i915/intel_engine_cs.c | 10 +++++++---
> 2 files changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> index e838c765b251..4de0a52f14a9 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -1923,8 +1923,8 @@ static int i915_gem_framebuffer_info(struct seq_file *m, void *data)
>
> static void describe_ctx_ring(struct seq_file *m, struct intel_ring *ring)
> {
> - seq_printf(m, " (ringbuffer, space: %d, head: %u, tail: %u)",
> - ring->space, ring->head, ring->tail);
> + seq_printf(m, " (ringbuffer, space: %d, head: %u, tail: %u, emit: %u)",
> + ring->space, ring->head, ring->tail, ring->emit);
> }
>
> static int i915_context_status(struct seq_file *m, void *unused)
> diff --git a/drivers/gpu/drm/i915/intel_engine_cs.c b/drivers/gpu/drm/i915/intel_engine_cs.c
> index 4ba139c27fba..e71bd6951d9b 100644
> --- a/drivers/gpu/drm/i915/intel_engine_cs.c
> +++ b/drivers/gpu/drm/i915/intel_engine_cs.c
> @@ -1929,12 +1929,16 @@ void intel_engine_dump(struct intel_engine_cs *engine,
> rq->head, rq->postfix, rq->tail,
> rq->batch ? upper_32_bits(rq->batch->node.start) : ~0u,
> rq->batch ? lower_32_bits(rq->batch->node.start) : ~0u);
> - drm_printf(m, "\t\tring->start: 0x%08x\n",
> + drm_printf(m, "\t\tring->start : 0x%08x\n",
Please check the space before ':', seems unintentional.
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> i915_ggtt_offset(rq->ring->vma));
> - drm_printf(m, "\t\tring->head: 0x%08x\n",
> + drm_printf(m, "\t\tring->head: 0x%08x\n",
> rq->ring->head);
> - drm_printf(m, "\t\tring->tail: 0x%08x\n",
> + drm_printf(m, "\t\tring->tail: 0x%08x\n",
> rq->ring->tail);
> + drm_printf(m, "\t\tring->emit: 0x%08x\n",
> + rq->ring->emit);
> + drm_printf(m, "\t\tring->space: 0x%08x\n",
> + rq->ring->space);
> }
>
> rcu_read_unlock();
> --
> 2.16.2
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-03-09 13:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 13:42 [PATCH 1/6] drm/i915: Finish the wait-for-wedge by retiring all the inflight requests Chris Wilson
2018-03-07 13:42 ` [PATCH 2/6] drm/i915: Reset ring space estimate after unwinding the request Chris Wilson
2018-03-09 13:17 ` Mika Kuoppala
2018-03-09 13:42 ` Chris Wilson
2018-03-09 13:20 ` Chris Wilson
2018-03-07 13:42 ` [PATCH 3/6] drm/i915: Update ring position from request on retiring Chris Wilson
2018-03-09 13:38 ` Mika Kuoppala
2018-03-09 13:56 ` Chris Wilson
2018-03-07 13:42 ` [PATCH 4/6] drm/i915: Include ring->emit in debugging Chris Wilson
2018-03-09 13:41 ` Mika Kuoppala [this message]
2018-03-07 13:42 ` [PATCH 5/6] drm/i915: Wrap engine->schedule in RCU locks for set-wedge protection Chris Wilson
2018-03-09 13:49 ` Mika Kuoppala
2018-03-07 13:42 ` [PATCH 6/6] drm/i915: Only call tasklet_kill() on the first prepare_reset Chris Wilson
2018-03-09 14:01 ` Mika Kuoppala
2018-03-09 14:10 ` Chris Wilson
2018-03-09 14:22 ` Chris Wilson
2018-03-07 14:31 ` ✓ Fi.CI.BAT: success for series starting with [1/6] drm/i915: Finish the wait-for-wedge by retiring all the inflight requests Patchwork
2018-03-07 16:55 ` ✓ Fi.CI.IGT: " Patchwork
2018-03-09 12:54 ` [PATCH 1/6] " Mika Kuoppala
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=87zi3hmkmr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox