From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Intel-gfx@lists.freedesktop.org
Cc: Rob Clark <robdclark@chromium.org>
Subject: [Intel-gfx] [PATCH 0/8] Per client GPU utilisation
Date: Tue, 22 Feb 2022 14:04:14 +0000 [thread overview]
Message-ID: <20220222140422.1121163-1-tvrtko.ursulin@linux.intel.com> (raw)
From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Rebase with a few small tweaks of the same old work.
Main highlight is that I have now posted a vendor agnostic IGT/tools/gputop as
well (https://patchwork.freedesktop.org/series/100571/).
Now mostly reviewed and waiting for some r-b updates and a confirmation the
vendor agnostic bit can truly live up to that goal.
Example of the intel_gpu_top output:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
intel-gpu-top: Intel Tigerlake (Gen12) @ /dev/dri/card0 - 220/ 221 MHz
70% RC6; 0.62/ 7.08 W; 760 irqs/s
ENGINES BUSY MI_SEMA MI_WAIT
Render/3D 23.06% |██████▊ | 0% 0%
Blitter 0.00% | | 0% 0%
Video 5.40% |█▋ | 0% 0%
VideoEnhance 20.67% |██████ | 0% 0%
PID NAME Render/3D Blitter Video VideoEnhance
3082 mpv | || ||▌ ||██ |
3117 neverball |█▉ || || || |
1 systemd |▍ || || || |
2338 gnome-shell | || || || |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Example of the gputop output:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DRM minor 0
PID NAME render copy video
3816 kwin_x11 |███▎ || || || |
3523 Xorg |▊ || || || |
1120449 mpv | || ||▋ || |
1120529 glxgears |▋ || || || |
1120449 mpv |▍ || || || |
3860 plasmashell |▏ || || || |
4764 krunner | || || || |
575206 chrome | || || || |
833481 firefox | || || || |
892924 thunderbird | || || || |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
v2:
* Added prototype of possible amdgpu changes and spec updates to align with the
common spec.
v3:
* Documented that 'drm-driver' tag shall correspond with
struct drm_driver.name.
v4:
* Dropped amdgpu conversion from the series for now until AMD folks can find
some time to finish that patch.
v5:
* Added drm-engine-capacity-* tag.
* Couple small tweaks.
Test-with: 20220222135605.1120767-1-tvrtko.ursulin@linux.intel.com
Tvrtko Ursulin (8):
drm/i915: Explicitly track DRM clients
drm/i915: Make GEM contexts track DRM clients
drm/i915: Track runtime spent in closed and unreachable GEM contexts
drm/i915: Track all user contexts per client
drm/i915: Track context current active time
drm: Document fdinfo format specification
drm/i915: Count engine instances per uabi class
drm/i915: Expose client engine utilisation via fdinfo
Documentation/gpu/drm-usage-stats.rst | 112 +++++++++++++
Documentation/gpu/i915.rst | 28 ++++
Documentation/gpu/index.rst | 1 +
drivers/gpu/drm/i915/Makefile | 1 +
drivers/gpu/drm/i915/gem/i915_gem_context.c | 42 ++++-
.../gpu/drm/i915/gem/i915_gem_context_types.h | 6 +
drivers/gpu/drm/i915/gt/intel_context.c | 27 +++-
drivers/gpu/drm/i915/gt/intel_context.h | 15 +-
drivers/gpu/drm/i915/gt/intel_context_types.h | 24 ++-
drivers/gpu/drm/i915/gt/intel_engine_user.c | 11 +-
.../drm/i915/gt/intel_execlists_submission.c | 23 ++-
.../gpu/drm/i915/gt/intel_gt_clock_utils.c | 4 +
drivers/gpu/drm/i915/gt/intel_lrc.c | 27 ++--
drivers/gpu/drm/i915/gt/intel_lrc.h | 27 +++-
drivers/gpu/drm/i915/gt/selftest_lrc.c | 10 +-
drivers/gpu/drm/i915/i915_driver.c | 9 ++
drivers/gpu/drm/i915/i915_drm_client.c | 151 ++++++++++++++++++
drivers/gpu/drm/i915/i915_drm_client.h | 68 ++++++++
drivers/gpu/drm/i915/i915_drv.h | 4 +
drivers/gpu/drm/i915/i915_file_private.h | 3 +
drivers/gpu/drm/i915/i915_gem.c | 21 ++-
drivers/gpu/drm/i915/i915_gpu_error.c | 9 +-
drivers/gpu/drm/i915/i915_gpu_error.h | 2 +-
23 files changed, 565 insertions(+), 60 deletions(-)
create mode 100644 Documentation/gpu/drm-usage-stats.rst
create mode 100644 drivers/gpu/drm/i915/i915_drm_client.c
create mode 100644 drivers/gpu/drm/i915/i915_drm_client.h
--
2.32.0
next reply other threads:[~2022-02-22 14:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 14:04 Tvrtko Ursulin [this message]
2022-02-22 14:04 ` [Intel-gfx] [PATCH 1/8] drm/i915: Explicitly track DRM clients Tvrtko Ursulin
2022-02-22 14:04 ` [Intel-gfx] [PATCH 2/8] drm/i915: Make GEM contexts " Tvrtko Ursulin
2022-02-22 14:04 ` [Intel-gfx] [PATCH 3/8] drm/i915: Track runtime spent in closed and unreachable GEM contexts Tvrtko Ursulin
2022-02-22 14:04 ` [Intel-gfx] [PATCH 4/8] drm/i915: Track all user contexts per client Tvrtko Ursulin
2022-02-22 14:04 ` [Intel-gfx] [PATCH 5/8] drm/i915: Track context current active time Tvrtko Ursulin
2022-02-22 14:04 ` [Intel-gfx] [PATCH 6/8] drm: Document fdinfo format specification Tvrtko Ursulin
2022-02-22 14:04 ` [Intel-gfx] [PATCH 7/8] drm/i915: Count engine instances per uabi class Tvrtko Ursulin
2022-03-01 19:34 ` Umesh Nerlige Ramappa
2022-03-02 9:03 ` Tvrtko Ursulin
2022-03-04 0:06 ` Umesh Nerlige Ramappa
2022-02-22 14:04 ` [Intel-gfx] [PATCH 8/8] drm/i915: Expose client engine utilisation via fdinfo Tvrtko Ursulin
2022-03-01 17:40 ` Rob Clark
2022-02-22 21:58 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Per client GPU utilisation Patchwork
2022-02-22 21:59 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-22 22:03 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-02-22 22:27 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-23 8:52 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-02-23 22:44 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Per client GPU utilisation (rev2) Patchwork
2022-02-23 22:45 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-23 22:49 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-02-23 23:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-24 10:41 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-03-31 14:09 [Intel-gfx] [PATCH 0/8] Per client GPU utilisation 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=20220222140422.1121163-1-tvrtko.ursulin@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=robdclark@chromium.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