From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Cc: Intel-gfx@lists.freedesktop.org,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: Re: [igt-dev] [RFC i-g-t 1/1] intel-gpu-top: Support for client stats
Date: Fri, 25 Oct 2019 16:38:55 +0100 [thread overview]
Message-ID: <12639e47-d31a-5f58-33d0-ed37023e2f77@linux.intel.com> (raw)
In-Reply-To: <157201643536.11797.12701857221082778286@skylake-alporthouse-com>
On 25/10/2019 16:13, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2019-10-25 15:24:10)
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> Adds support for per-client engine busyness stats i915 exports in sysfs
>> and produces output like the below:
>>
>> ==========================================================================
>> intel-gpu-top - 935/ 935 MHz; 0% RC6; 14.73 Watts; 1097 irqs/s
>
> Could we get "gpu / pkg Watts" pretty please?
Sure, next week or so.
> Are irq/s interesting with execlists? Originally the idea was to say how
> many times clients were sleeping and being woken up. Now we interrupt
> to wipe the gpu's nose when it sneezes.
>
>>
>> IMC reads: 1401 MiB/s
>> IMC writes: 4 MiB/s
>>
>> ENGINE BUSY MI_SEMA MI_WAIT
>> Render/3D/0 63.73% |███████████████████ | 3% 0%
>> Blitter/0 9.53% |██▊ | 6% 0%
>> Video/0 39.32% |███████████▊ | 16% 0%
>> Video/1 15.62% |████▋ | 0% 0%
>> VideoEnhance/0 0.00% | | 0% 0%
>>
>> PID NAME RCS BCS VCS VECS
>> 4084 gem_wsim |█████▌ ||█ || || |
>> 4086 gem_wsim |█▌ || ||███ || |
>> ==========================================================================
>>
>> Apart from the existing physical engine utilization it now also shows
>> utilization per client and per engine class.
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> ---
>
>> +#define SYSFS_CLIENTS "/sys/class/drm/card0/clients"
>
> We need to somehow pull the right card.
Yeah, as I said RFC and reference only. :)
> Nothing shocking here. Where's the intel-gpu-overlay integration? ;)
Maybe intel-gpu-overlay should become an output plugin for intel_gpu_top. :)
Regards,
Tvrtko
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-10-25 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 14:24 [igt-dev] [RFC i-g-t 0/1] Per client engine busyness Tvrtko Ursulin
2019-10-25 14:24 ` [igt-dev] [RFC i-g-t 1/1] intel-gpu-top: Support for client stats Tvrtko Ursulin
2019-10-25 15:13 ` Chris Wilson
2019-10-25 15:38 ` Tvrtko Ursulin [this message]
2019-10-25 15:26 ` [igt-dev] ✓ Fi.CI.BAT: success for Per client engine busyness Patchwork
2019-10-27 5:50 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2020-03-09 18:32 [Intel-gfx] [RFC i-g-t 0/1] Per client intel_gpu_top Tvrtko Ursulin
2020-03-09 18:32 ` [igt-dev] [RFC i-g-t 1/1] intel-gpu-top: Support for client stats Tvrtko Ursulin
2019-05-10 13:23 [igt-dev] [RFC i-g-t 0/1] intel_gpu_top: Per-client engine busyness Tvrtko Ursulin
2019-05-10 13:23 ` [igt-dev] [RFC i-g-t 1/1] intel-gpu-top: Support for client stats Tvrtko Ursulin
2019-05-10 15:33 ` Chris Wilson
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=12639e47-d31a-5f58-33d0-ed37023e2f77@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=tvrtko.ursulin@intel.com \
/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