All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Olinski, Krzysztof E" <krzysztof.e.olinski@intel.com>
To: "tursulin@ursulin.net" <tursulin@ursulin.net>,
	"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>
Cc: "Intel-gfx@lists.freedesktop.org" <Intel-gfx@lists.freedesktop.org>
Subject: Re: [RFC i-g-t] igt/scripts: trace.pl to parse the i915 tracepoints
Date: Wed, 22 Feb 2017 11:58:49 +0000	[thread overview]
Message-ID: <1487764727.11936.3.camel@intel.com> (raw)
In-Reply-To: <20170222101011.GI10557@nuc-i3427.alporthouse.com>


[-- Attachment #1.1: Type: text/plain, Size: 1107 bytes --]

On Wed, 2017-02-22 at 10:10 +0000, Chris Wilson wrote:
> On Wed, Feb 22, 2017 at 10:03:33AM +0000, Tvrtko Ursulin wrote:
> > From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> > 
> > Given a log file created via perf with some interesting trace
> > events enabled, this tool can generate the timeline graph of
> > requests getting queued, their dependencies resolved, sent to
> > the GPU for executing and finally completed.
> > 
> > This can be useful when analyzing certain classes of performance
> > issues. More help is available in the tool itself.
> > 
> > The tool will also calculate some overall per engine statistics,
> > like total time engine was idle and similar.
> > 
> > Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> > ---
> > A bit rough around the edges but works for the majority of traces
> > I was feeding into it.
> > 
> > Wheter or not we want to add this to IGT I am not sure.
> 
> It has my vote.
> -Chris
> 

Definitely, this will be valuable - good starting point for undergoing
core perf validation efforts.

Thanks for sharing,
Krzysztof

[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3290 bytes --]

[-- Attachment #2.1: Type: text/plain, Size: 846 bytes --]

--------------------------------------------------------------------

Intel Technology Poland sp. z o.o.
ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000 PLN.

Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek
przegladanie lub rozpowszechnianie jest zabronione.
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by
others is strictly prohibited.

[-- Attachment #2.2: Type: text/html, Size: 1553 bytes --]

[-- Attachment #3: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2017-02-22 11:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 10:03 [RFC i-g-t] igt/scripts: trace.pl to parse the i915 tracepoints Tvrtko Ursulin
2017-02-22 10:10 ` Chris Wilson
2017-02-22 11:58   ` Olinski, Krzysztof E [this message]

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=1487764727.11936.3.camel@intel.com \
    --to=krzysztof.e.olinski@intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=tursulin@ursulin.net \
    /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.