From: Soham Purkait <soham.purkait@intel.com>
To: igt-dev@lists.freedesktop.org, riana.tauro@intel.com,
vinay.belgaumkar@intel.com
Cc: anshuman.gupta@intel.com, lucas.demarchi@intel.com,
rodrigo.vivi@intel.com, soham.purkait@intel.com,
jonathan.ming.jun.lui@intel.com
Subject: [PATCH i-g-t v3 0/4] Add single engine busyness stats in GPUTOP
Date: Fri, 28 Feb 2025 19:48:06 +0530 [thread overview]
Message-ID: <20250228141810.1417657-1-soham.purkait@intel.com> (raw)
Add single engine busyness support in GPUTOP. This uses
the PMU interface to display the busyness of each
engine instances.
This patch refactors GPUTOP to be vendor-agnostic,
laying the groundwork for future support of multiple
GPU vendors.
Currently, GPUTOP supports GPUs with Xe driver only and can
monitor the engine busyness of multiple GPU devices
simultaneously through abstracting vendor-specific code
into a common interface and implementing vendor-neutral
APIs for monitoring.
DRIVER: xe || SLOT: 0000:00:02.0
ENGINES BUSY
Render/3D/0 | 96.5% ███████████████████████████████████████ |
Blitter/0 | 91.6% █████████████████████████████████████ |
Video/0 | 56.2% ███████████████████████████ |
VideoEnhance/0| 97.7% ████████████████████████████████████████|
Compute/0 | 48.5% ███████████████████████ |
Soham Purkait (4):
lib/igt_device_scan: Enable finding all IGT devices for xe driver
tools/gputop/common_gputop: Add gputop functionality common to all drivers
tools/gputop/xe_gputop: Add gputop support for xe specific devices
tools/gputop: Enable support for multiple GPUs and instances
lib/igt_device_scan.c | 97 +++++++++
lib/igt_device_scan.h | 3 +
tools/gputop/common_gputop.c | 79 +++++++
tools/gputop/common_gputop.h | 58 +++++
tools/{ => gputop}/gputop.c | 203 ++++++++++++++----
tools/gputop/meson.build | 6 +
tools/gputop/xe_gputop.c | 404 +++++++++++++++++++++++++++++++++++
tools/gputop/xe_gputop.h | 74 +++++++
tools/meson.build | 6 +-
9 files changed, 881 insertions(+), 49 deletions(-)
create mode 100644 tools/gputop/common_gputop.c
create mode 100644 tools/gputop/common_gputop.h
rename tools/{ => gputop}/gputop.c (71%)
create mode 100644 tools/gputop/meson.build
create mode 100644 tools/gputop/xe_gputop.c
create mode 100644 tools/gputop/xe_gputop.h
--
2.34.1
next reply other threads:[~2025-02-28 14:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 14:18 Soham Purkait [this message]
2025-02-28 14:18 ` [PATCH i-g-t v3 1/4] Enable finding all IGT devices for xe driver Soham Purkait
2025-02-28 16:58 ` Lucas De Marchi
2025-02-28 14:18 ` [PATCH i-g-t v3 2/4] Add gputop functionality common to all drivers Soham Purkait
2025-03-04 10:07 ` Riana Tauro
2025-02-28 14:18 ` [PATCH i-g-t v3 3/4] Add gputop support for xe specific devices Soham Purkait
2025-03-04 10:22 ` Riana Tauro
2025-02-28 14:18 ` [PATCH i-g-t v3 4/4] Enable support for multiple GPUs and instances Soham Purkait
2025-02-28 22:37 ` ✓ i915.CI.BAT: success for Add single engine busyness stats in GPUTOP (rev4) Patchwork
2025-02-28 23:06 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-01 7:45 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-01 11:23 ` ✗ i915.CI.Full: " 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=20250228141810.1417657-1-soham.purkait@intel.com \
--to=soham.purkait@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jonathan.ming.jun.lui@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=vinay.belgaumkar@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