From: John Harrison <John.C.Harrison@Intel.com>
To: Tvrtko Ursulin <tursulin@ursulin.net>, igt-dev@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 3/9] trace.pl: Improve readability of graphical timeline representation
Date: Thu, 12 Jul 2018 17:51:20 -0700 [thread overview]
Message-ID: <52ac60f9-ea11-cbd2-6f72-2bae0656d19a@Intel.com> (raw)
In-Reply-To: <20180712105958.12953-4-tvrtko.ursulin@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1002 bytes --]
On 7/12/2018 3:59 AM, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> We add stripes for different stages of request execution so it is easier
> to follow one context in the multi-colour mode.
>
> Vertical stripe pattern indicates pipeline "blockages" - requests waiting
> for dependencies before they are runnable.
>
> Diagonal stripes indicate runnable requests waiting for GPU time.
>
> Horizontal strips are requests executing on the GPU.
>
> Also use this new multi-coloured mode from media-bench.pl.
>
> v2:
> John Harrison:
> * Mention media-bench.pl in the commit.
> * Fix HTML for single colour mode.
>
> v3:
> * Rebase.
> * Apply stripes to legacy colouring as well.
>
> v4:
> John Harrison:
> * Use per context colours for ctxsave and incomplete boxes.
> * Clearer timeline legend.
>
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: John Harrison <John.C.Harrison@Intel.com>
Reviewed-by: John Harrison<John.C.Harrison@Intel.com>
[-- Attachment #1.2: Type: text/html, Size: 1616 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: John Harrison <John.C.Harrison@Intel.com>
To: Tvrtko Ursulin <tursulin@ursulin.net>, igt-dev@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH i-g-t 3/9] trace.pl: Improve readability of graphical timeline representation
Date: Thu, 12 Jul 2018 17:51:20 -0700 [thread overview]
Message-ID: <52ac60f9-ea11-cbd2-6f72-2bae0656d19a@Intel.com> (raw)
In-Reply-To: <20180712105958.12953-4-tvrtko.ursulin@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1002 bytes --]
On 7/12/2018 3:59 AM, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> We add stripes for different stages of request execution so it is easier
> to follow one context in the multi-colour mode.
>
> Vertical stripe pattern indicates pipeline "blockages" - requests waiting
> for dependencies before they are runnable.
>
> Diagonal stripes indicate runnable requests waiting for GPU time.
>
> Horizontal strips are requests executing on the GPU.
>
> Also use this new multi-coloured mode from media-bench.pl.
>
> v2:
> John Harrison:
> * Mention media-bench.pl in the commit.
> * Fix HTML for single colour mode.
>
> v3:
> * Rebase.
> * Apply stripes to legacy colouring as well.
>
> v4:
> John Harrison:
> * Use per context colours for ctxsave and incomplete boxes.
> * Clearer timeline legend.
>
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: John Harrison <John.C.Harrison@Intel.com>
Reviewed-by: John Harrison<John.C.Harrison@Intel.com>
[-- Attachment #1.2: Type: text/html, Size: 1616 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-07-13 0:51 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 10:59 [PATCH i-g-t 0/9] trace.pl fixes and improvements Tvrtko Ursulin
2018-07-12 10:59 ` [igt-dev] " Tvrtko Ursulin
2018-07-12 10:59 ` [PATCH i-g-t 1/9] trace.pl: Improve time axis labels Tvrtko Ursulin
2018-07-12 10:59 ` [igt-dev] " Tvrtko Ursulin
2018-07-12 12:42 ` Tvrtko Ursulin
2018-07-12 12:42 ` Tvrtko Ursulin
2018-07-12 22:35 ` John Harrison
2018-07-12 22:35 ` John Harrison
2018-07-13 9:55 ` [PATCH i-g-t v2 " Tvrtko Ursulin
2018-07-13 9:55 ` [igt-dev] " Tvrtko Ursulin
2018-07-16 17:53 ` John Harrison
2018-07-16 17:53 ` [Intel-gfx] " John Harrison
2018-07-17 8:56 ` [igt-dev] " Tvrtko Ursulin
2018-07-17 8:56 ` [Intel-gfx] " Tvrtko Ursulin
2018-07-17 15:11 ` John Harrison
2018-07-17 15:11 ` John Harrison
2018-07-17 15:31 ` John Harrison
2018-07-17 15:31 ` John Harrison
2018-07-17 16:22 ` Tvrtko Ursulin
2018-07-17 16:22 ` Tvrtko Ursulin
2018-07-17 17:57 ` John Harrison
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-12 10:59 ` [igt-dev] " Tvrtko Ursulin
2018-07-13 0:21 ` John Harrison
2018-07-13 0:21 ` [igt-dev] " John Harrison
2018-07-13 10:02 ` [PATCH i-g-t v3 " Tvrtko Ursulin
2018-07-13 10:02 ` [igt-dev] " Tvrtko Ursulin
2018-07-16 18:15 ` John Harrison
2018-07-16 18:15 ` [igt-dev] " 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-12 10:59 ` [igt-dev] " Tvrtko Ursulin
2018-07-13 0:51 ` John Harrison [this message]
2018-07-13 0:51 ` [Intel-gfx] " 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-12 10:59 ` [igt-dev] " Tvrtko Ursulin
2018-07-13 0:51 ` John Harrison
2018-07-13 0:51 ` [Intel-gfx] " John Harrison
2018-07-12 10:59 ` [PATCH i-g-t 5/9] trace.pl: Improved key/colours Tvrtko Ursulin
2018-07-12 10:59 ` [igt-dev] " Tvrtko Ursulin
2018-07-12 11:03 ` Tvrtko Ursulin
2018-07-12 11:03 ` Tvrtko Ursulin
2018-07-13 0:52 ` John Harrison
2018-07-13 0:52 ` [igt-dev] " John Harrison
2018-07-13 9:56 ` [PATCH i-g-t v3 " Tvrtko Ursulin
2018-07-13 9:56 ` [igt-dev] " Tvrtko Ursulin
2018-07-14 0:01 ` John Harrison
2018-07-14 0:01 ` [igt-dev] " John Harrison
2018-07-16 8:49 ` [PATCH i-g-t v4 " Tvrtko Ursulin
2018-07-16 8:49 ` [Intel-gfx] " Tvrtko Ursulin
2018-07-16 19:11 ` John Harrison
2018-07-16 19:11 ` [igt-dev] " 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 ` [igt-dev] " Tvrtko Ursulin
2018-07-13 6:55 ` John Harrison
2018-07-12 10:59 ` [PATCH i-g-t 7/9] trace.pl: Fix incomplete request handling Tvrtko Ursulin
2018-07-12 10:59 ` [igt-dev] " Tvrtko Ursulin
2018-07-13 7:00 ` John Harrison
2018-07-13 7:00 ` [igt-dev] " 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 ` [igt-dev] " Tvrtko Ursulin
2018-07-13 0:54 ` John Harrison
2018-07-12 10:59 ` [PATCH i-g-t 9/9] trace.pl: Fix request split mode Tvrtko Ursulin
2018-07-12 10:59 ` [igt-dev] " Tvrtko Ursulin
2018-07-12 14:26 ` [igt-dev] ✓ Fi.CI.BAT: success for trace.pl fixes and improvements (rev3) Patchwork
2018-07-12 15:50 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-07-13 11:09 ` [igt-dev] ✓ Fi.CI.BAT: success for trace.pl fixes and improvements (rev6) Patchwork
2018-07-13 13:59 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2018-07-16 10:03 ` [igt-dev] ✓ Fi.CI.BAT: success for trace.pl fixes and improvements (rev7) Patchwork
2018-07-16 16:41 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=52ac60f9-ea11-cbd2-6f72-2bae0656d19a@Intel.com \
--to=john.c.harrison@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--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.