From: Tvrtko Ursulin <tursulin@ursulin.net>
To: Intel-gfx@lists.freedesktop.org
Subject: [RFC 0/5] Per-client engine stats
Date: Wed, 14 Feb 2018 18:50:30 +0000 [thread overview]
Message-ID: <20180214185035.8010-1-tvrtko.ursulin@linux.intel.com> (raw)
From: Tvrtko Ursulin <tvrtko.ursulin@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 9.47, 3.34, 0.13; 1000/ 950 MHz; 0% RC6; 5202mW; 1206 irqs/s
rcs0 100.00% ( 0.56/ 4.78/ 3.86) |██████████████████████████████████████████████████████████████████| 0.00% wait, 0.00% sema
bcs0 17.72% ( 0.81/ 0.00/ 0.17) |███████████▋ | 0.00% wait, 0.00% sema
vcs0 61.08% ( 0.81/ 0.00/ 0.63) |████████████████████████████████████████▎ | 0.00% wait, 0.00% sema
vecs0 0.00% ( 0.00/ 0.00/ 0.00) | | 0.00% wait, 0.00% sema
PID NAME rcs0 bcs0 vcs0 vecs0
9654 neverball |████████████ || || || |
7792 Xorg |████████▊ || || || |
9659 gem_wsim |████ ||████▍ ||███████████████▎ || |
7846 xfwm4 | || || || |
I'll post the IGT support for this as well. It requires both this series and
engine queue depth PMU RFC-ed recently.
Tvrtko Ursulin (5):
drm/i915: Track per-context engine busyness
drm/i915: Expose list of clients in sysfs
drm/i915: Update client name on context create
drm/i915: Expose per-engine client busyness
drm/i915: Add sysfs toggle to enable per-client engine stats
drivers/gpu/drm/i915/i915_drv.h | 31 ++++++
drivers/gpu/drm/i915/i915_gem.c | 192 ++++++++++++++++++++++++++++++--
drivers/gpu/drm/i915/i915_gem_context.c | 23 +++-
drivers/gpu/drm/i915/i915_gem_context.h | 7 ++
drivers/gpu/drm/i915/i915_sysfs.c | 80 +++++++++++++
drivers/gpu/drm/i915/intel_engine_cs.c | 29 +++++
drivers/gpu/drm/i915/intel_lrc.c | 14 ++-
drivers/gpu/drm/i915/intel_ringbuffer.h | 56 +++++++++-
8 files changed, 412 insertions(+), 20 deletions(-)
--
2.14.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2018-02-14 18:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 18:50 Tvrtko Ursulin [this message]
2018-02-14 18:50 ` [RFC 1/5] drm/i915: Track per-context engine busyness Tvrtko Ursulin
2018-02-14 19:07 ` Chris Wilson
2018-02-15 9:29 ` Tvrtko Ursulin
2018-02-15 9:35 ` Chris Wilson
2018-02-14 18:50 ` [RFC 2/5] drm/i915: Expose list of clients in sysfs Tvrtko Ursulin
2018-02-14 19:13 ` Chris Wilson
2018-02-15 9:35 ` Tvrtko Ursulin
2018-02-14 18:50 ` [RFC 3/5] drm/i915: Update client name on context create Tvrtko Ursulin
2018-02-14 18:50 ` [RFC 4/5] drm/i915: Expose per-engine client busyness Tvrtko Ursulin
2018-02-14 19:17 ` Chris Wilson
2018-02-15 9:41 ` Tvrtko Ursulin
2018-02-15 9:44 ` Chris Wilson
2018-02-15 15:13 ` Tvrtko Ursulin
2018-02-14 18:50 ` [RFC 5/5] drm/i915: Add sysfs toggle to enable per-client engine stats Tvrtko Ursulin
2018-02-14 18:55 ` ✗ Fi.CI.CHECKPATCH: warning for Per-client " Patchwork
2018-02-14 19:11 ` ✓ Fi.CI.BAT: success " Patchwork
2018-02-14 19:20 ` [RFC 0/5] " Chris Wilson
2018-02-15 9:44 ` Tvrtko Ursulin
2018-02-15 9:47 ` Chris Wilson
2018-02-15 10:50 ` Tvrtko Ursulin
2018-02-15 2:19 ` ✓ Fi.CI.IGT: success for " 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=20180214185035.8010-1-tvrtko.ursulin@linux.intel.com \
--to=tursulin@ursulin.net \
--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