From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gt: Include context status in debug dumps
Date: Wed, 10 Jun 2020 18:39:59 +0300 [thread overview]
Message-ID: <874krj9bg0.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20200610154046.22449-1-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> This may be useful to identify contexts that are running even though
> they are supposed to be closed or banned.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_engine_cs.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_engine_cs.c b/drivers/gpu/drm/i915/gt/intel_engine_cs.c
> index 72f0029d490b..6d0a8ac02fb4 100644
> --- a/drivers/gpu/drm/i915/gt/intel_engine_cs.c
> +++ b/drivers/gpu/drm/i915/gt/intel_engine_cs.c
> @@ -1423,9 +1423,11 @@ static void intel_engine_print_registers(struct intel_engine_cs *engine,
> int len;
>
> len = scnprintf(hdr, sizeof(hdr),
> - "\t\tActive[%d]: ccid:%08x, ",
> + "\t\tActive[%d]: ccid:%08x%s%s, ",
> (int)(port - execlists->active),
> - rq->context->lrc.ccid);
> + rq->context->lrc.ccid,
> + intel_context_is_closed(rq->context) ? "!" : "",
> + intel_context_is_banned(rq->context) ? "*" : "");
> len += print_ring(hdr + len, sizeof(hdr) - len, rq);
> scnprintf(hdr + len, sizeof(hdr) - len, "rq: ");
> print_request(m, rq, hdr);
> @@ -1435,9 +1437,11 @@ static void intel_engine_print_registers(struct intel_engine_cs *engine,
> int len;
>
> len = scnprintf(hdr, sizeof(hdr),
> - "\t\tPending[%d]: ccid:%08x, ",
> + "\t\tPending[%d]: ccid:%08x%s%s, ",
> (int)(port - execlists->pending),
> - rq->context->lrc.ccid);
> + rq->context->lrc.ccid,
> + intel_context_is_closed(rq->context) ? "!" : "",
> + intel_context_is_banned(rq->context) ? "*" : "");
> len += print_ring(hdr + len, sizeof(hdr) - len, rq);
> scnprintf(hdr + len, sizeof(hdr) - len, "rq: ");
> print_request(m, rq, hdr);
> --
> 2.20.1
>
> _______________________________________________
> 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:[~2020-06-10 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 15:40 [Intel-gfx] [PATCH] drm/i915/gt: Include context status in debug dumps Chris Wilson
2020-06-10 15:39 ` Mika Kuoppala [this message]
2020-06-10 17:15 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-06-11 10:26 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=874krj9bg0.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.