[Intel-gfx] [RFC v4 0/7] Per-context and per-client engine busyness
Chris Wilson
chris at chris-wilson.co.uk
Tue Apr 17 12:39:55 UTC 2018
Quoting Tvrtko Ursulin (2018-04-17 13:27:29)
> From: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
>
> Another re-post of my earlier, now slightly updated work, to expose a DRM client
> hierarchy in sysfs in order to enable a top like tool:
>
> intel-gpu-top - load avg 40.80, 27.11, 1.50; 882/ 950 MHz; 0% RC6; 13.26 Watts; 261903 irqs/s
>
> IMC reads: 5543 MiB/s
> IMC writes: 236 MiB/s
>
> ENGINE BUSY QD MI_SEMA MI_WAIT
QD could do with more explanation, maybe like so?
ENGINE BUSY E Q W MI_SEMA MI_WAIT
> Render/3D/0 60.47% |███████████▍ | 28 0 1 0% 0%
Render/Compute?
Another visual break after QD?
Render/Compute/0 60.47% |███████████▍ | 28 0 1 | 0% 0%
> Blitter/0 92.70% |█████████████████▌ | 0 0 1 0% 0%
> Video/0 100.00% |███████████████████| 15 37 2 0% 0%
> Video/1 51.68% |█████████▊ | 0 0 1 0% 0%
> VideoEnhance/0 0.00% | | 0 0 0 0% 0%
>
> PID NAME rcs0 bcs0 vcs0 vcs1 vecs0
> 21664 gem_wsim |█████▍ || ||█████████||████▋ || |
> 21662 gem_latency | ||████████▎|| || || |
> 21662 gem_latency | || || || || |
-Chris
More information about the Intel-gfx
mailing list