Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tursulin@ursulin.net>
To: igt-dev@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: [PATCH i-g-t 0/9] trace.pl fixes and improvements
Date: Thu, 12 Jul 2018 11:59:49 +0100	[thread overview]
Message-ID: <20180712105958.12953-1-tvrtko.ursulin@linux.intel.com> (raw)

From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

Latest state of patches preceding the virtual engine support.

John Harrison (1):
  trace.pl: Improved key/colours

Tvrtko Ursulin (8):
  trace.pl: Improve time axis labels
  trace.pl: Scale timeline for better precision
  trace.pl: Improve readability of graphical timeline representation
  trace.pl: Improve context colouring for large context id's
  trace.pl: Context save only applies to last request of a bunch
  trace.pl: Fix incomplete request handling
  trace.pl: Basic preemption support
  trace.pl: Fix request split mode

 scripts/media-bench.pl |   2 +-
 scripts/trace.pl       | 541 ++++++++++++++++++++++++++++++++---------
 2 files changed, 425 insertions(+), 118 deletions(-)

-- 
2.17.1

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

             reply	other threads:[~2018-07-12 11:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-12 10:59 Tvrtko Ursulin [this message]
2018-07-12 10:59 ` [PATCH i-g-t 1/9] trace.pl: Improve time axis labels Tvrtko Ursulin
2018-07-12 12:42   ` [igt-dev] " Tvrtko Ursulin
2018-07-12 22:35     ` John Harrison
2018-07-13  9:55       ` [PATCH i-g-t v2 " Tvrtko Ursulin
2018-07-16 17:53         ` John Harrison
2018-07-17  8:56           ` [igt-dev] " Tvrtko Ursulin
2018-07-17 15:11             ` John Harrison
2018-07-17 15:31               ` John Harrison
2018-07-17 16:22                 ` Tvrtko Ursulin
2018-07-17 17:57                   ` John Harrison
2018-07-12 10:59 ` [PATCH i-g-t 2/9] trace.pl: Scale timeline for better precision Tvrtko Ursulin
2018-07-13  0:21   ` John Harrison
2018-07-13 10:02   ` [PATCH i-g-t v3 " Tvrtko Ursulin
2018-07-16 18:15     ` John Harrison
2018-07-12 10:59 ` [PATCH i-g-t 3/9] trace.pl: Improve readability of graphical timeline representation Tvrtko Ursulin
2018-07-13  0:51   ` John Harrison
2018-07-12 10:59 ` [PATCH i-g-t 4/9] trace.pl: Improve context colouring for large context id's Tvrtko Ursulin
2018-07-13  0:51   ` John Harrison
2018-07-12 10:59 ` [PATCH i-g-t 5/9] trace.pl: Improved key/colours Tvrtko Ursulin
2018-07-12 11:03   ` [igt-dev] " Tvrtko Ursulin
2018-07-13  0:52   ` John Harrison
2018-07-13  9:56     ` [PATCH i-g-t v3 " Tvrtko Ursulin
2018-07-14  0:01       ` John Harrison
2018-07-16  8:49         ` [PATCH i-g-t v4 " Tvrtko Ursulin
2018-07-16 19:11           ` John Harrison
2018-07-12 10:59 ` [PATCH i-g-t 6/9] trace.pl: Context save only applies to last request of a bunch Tvrtko Ursulin
2018-07-12 10:59 ` [PATCH i-g-t 7/9] trace.pl: Fix incomplete request handling Tvrtko Ursulin
2018-07-13  7:00   ` John Harrison
2018-07-12 10:59 ` [PATCH i-g-t 8/9] trace.pl: Basic preemption support Tvrtko Ursulin
2018-07-12 10:59 ` [PATCH i-g-t 9/9] trace.pl: Fix request split mode Tvrtko Ursulin

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=20180712105958.12953-1-tvrtko.ursulin@linux.intel.com \
    --to=tursulin@ursulin.net \
    --cc=igt-dev@lists.freedesktop.org \
    --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