All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/execlists: Add a GEM_TRACE to show when the context is completed
Date: Thu, 22 Feb 2018 10:50:23 +0200	[thread overview]
Message-ID: <87lgfls90w.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <151922736365.8092.2802319934418342848@mail.alporthouse.com>

Chris Wilson <chris@chris-wilson.co.uk> writes:

> Quoting Mika Kuoppala (2018-02-21 15:21:04)
>> Chris Wilson <chris@chris-wilson.co.uk> writes:
>> 
>> > Include a GEM_TRACE to show when the context is complete and we advance
>> > the ELSP port.
>> >
>> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>> > Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
>> > ---
>> >  drivers/gpu/drm/i915/intel_lrc.c | 3 +++
>> >  1 file changed, 3 insertions(+)
>> >
>> > diff --git a/drivers/gpu/drm/i915/intel_lrc.c b/drivers/gpu/drm/i915/intel_lrc.c
>> > index 9b6d781b22ec..fe5a0fa3f3b6 100644
>> > --- a/drivers/gpu/drm/i915/intel_lrc.c
>> > +++ b/drivers/gpu/drm/i915/intel_lrc.c
>> > @@ -890,6 +890,9 @@ static void execlists_submission_tasklet(unsigned long data)
>> >                               trace_i915_gem_request_out(rq);
>> >                               i915_gem_request_put(rq);
>> >  
>> > +                             GEM_TRACE("%s completed ctx=%d\n",
>> > +                                       engine->name, port->context_id);
>> > +
>> 
>> There is a trace above with a count so info is already there,
>> and could be amended to output completion if count == 1.
>
> But that assumes we don't add a bug in between. :)
>
> What I was thinking was that we really wanted to show the port
> advancement here, but not quite sure what to show. This gives us a clear
> marker for something to search for that doesn't require us to know that
> when count==1 we expect it to complete. Sometimes I like going easy on
> myself.

Agreed on here. It is hard enough to decode interactions
in the logs so being explicit and clear always helps.
-Mika
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-02-22  8:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 15:15 [PATCH] drm/i915/execlists: Add a GEM_TRACE to show when the context is completed Chris Wilson
2018-02-21 15:21 ` Mika Kuoppala
2018-02-21 15:36   ` Chris Wilson
2018-02-22  8:50     ` Mika Kuoppala [this message]
2018-02-21 15:47 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-02-21 19:44 ` ✓ 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=87lgfls90w.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.