From: Riana Tauro <riana.tauro@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: riana.tauro@intel.com, anshuman.gupta@intel.com,
umesh.nerlige.ramappa@intel.com, lucas.demarchi@intel.com,
vinay.belgaumkar@intel.com, soham.purkait@intel.com
Subject: [PATCH v6 0/8] PMU support for engine activity
Date: Tue, 11 Feb 2025 15:39:42 +0530 [thread overview]
Message-ID: <20250211100952.322303-1-riana.tauro@intel.com> (raw)
PMU provides two counters (engine-active-ticks, engine-total-ticks)
to calculate engine activity. When querying this, user must group
these 2 counters using the perf_event group mechanism to ensure
both counters are sampled together.
To list the events
./perf list
xe_0000_03_00.0/engine-active-ticks/ [Kernel PMU event]
xe_0000_03_00.0/engine-total-ticks/ [Kernel PMU event]
The formats to be used with the above are
gt - config:60-63
function - config:59-44
engine_class - config:20-27
engine_instance - config:12-19
The events can then be read using perf tool
./perf stat -e xe_<bdf>/engine-active-ticks,gt=<n>,engine_class=<n>,
engine_instance=<n>,function=<n>/,
xe_<bdf>/engine-total-ticks,gt=<n>,engine_class=<n>,
engine_instance=<n>,function<n>/
-I 1000
Engine activity can then be calculated as below
engine activity % = (engine active ticks/engine total ticks) * 100
Rev2: Add trace functions
fix cosmetic review comments
Rev3: add engine class and instance as parameters
replace busyness with engine activity
Rev4: add per-function engine activity
fix review comments
Rev5: Remove global for SRIOV
Add forcewake during init and destroy
fix other review comments
Rev6: fix review comments
Riana Tauro (8):
drm/xe: Add engine activity support
drm/xe/trace: Add trace for engine activity
drm/xe/guc: Expose engine activity only for supported GuC version
drm/xe/xe_pmu: Add PMU support for engine activity
drm/xe/xe_pmu: Acquire forcewake on event init for engine events
drm/xe: Add support for per-function engine activity
drm/xe/xe_pmu: Add PMU support for per-function engine activity stats
drm/xe/pf: Enable per-function engine activity stats
drivers/gpu/drm/xe/Makefile | 1 +
drivers/gpu/drm/xe/abi/guc_actions_abi.h | 2 +
drivers/gpu/drm/xe/regs/xe_gt_regs.h | 2 +
drivers/gpu/drm/xe/xe_guc.c | 5 +
drivers/gpu/drm/xe/xe_guc_engine_activity.c | 515 ++++++++++++++++++
drivers/gpu/drm/xe/xe_guc_engine_activity.h | 22 +
.../gpu/drm/xe/xe_guc_engine_activity_types.h | 98 ++++
drivers/gpu/drm/xe/xe_guc_fwif.h | 19 +
drivers/gpu/drm/xe/xe_guc_types.h | 4 +
drivers/gpu/drm/xe/xe_pci_sriov.c | 20 +
drivers/gpu/drm/xe/xe_pmu.c | 209 ++++++-
drivers/gpu/drm/xe/xe_pmu_types.h | 4 +
drivers/gpu/drm/xe/xe_trace_guc.h | 49 ++
drivers/gpu/drm/xe/xe_uc.c | 3 +
14 files changed, 940 insertions(+), 13 deletions(-)
create mode 100644 drivers/gpu/drm/xe/xe_guc_engine_activity.c
create mode 100644 drivers/gpu/drm/xe/xe_guc_engine_activity.h
create mode 100644 drivers/gpu/drm/xe/xe_guc_engine_activity_types.h
--
2.47.1
next reply other threads:[~2025-02-11 9:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 10:09 Riana Tauro [this message]
2025-02-11 10:09 ` [PATCH v6 1/8] drm/xe: Add engine activity support Riana Tauro
2025-02-11 10:09 ` [PATCH v6 2/8] drm/xe/trace: Add trace for engine activity Riana Tauro
2025-02-11 10:09 ` [PATCH v6 3/8] drm/xe/guc: Expose engine activity only for supported GuC version Riana Tauro
2025-02-13 18:08 ` Umesh Nerlige Ramappa
2025-02-11 10:09 ` [PATCH v6 4/8] drm/xe/xe_pmu: Add PMU support for engine activity Riana Tauro
2025-02-11 10:09 ` [PATCH v6 5/8] drm/xe/xe_pmu: Acquire forcewake on event init for engine events Riana Tauro
2025-02-12 23:49 ` Umesh Nerlige Ramappa
2025-02-11 10:09 ` [PATCH v6 6/8] drm/xe: Add support for per-function engine activity Riana Tauro
2025-02-11 10:09 ` [PATCH v6 7/8] drm/xe/xe_pmu: Add PMU support for per-function engine activity stats Riana Tauro
2025-02-11 10:09 ` [PATCH v6 8/8] drm/xe/pf: Enable " Riana Tauro
2025-02-11 10:48 ` ✓ CI.Patch_applied: success for PMU support for engine activity (rev2) Patchwork
2025-02-11 10:49 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-11 10:50 ` ✓ CI.KUnit: success " Patchwork
2025-02-11 11:19 ` ✓ CI.Build: " Patchwork
2025-02-11 11:21 ` ✗ CI.Hooks: failure " Patchwork
2025-02-11 11:22 ` ✗ CI.checksparse: warning " Patchwork
2025-02-11 11:42 ` ✓ Xe.CI.BAT: success " Patchwork
2025-02-11 19:01 ` ✗ Xe.CI.Full: failure " 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=20250211100952.322303-1-riana.tauro@intel.com \
--to=riana.tauro@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=soham.purkait@intel.com \
--cc=umesh.nerlige.ramappa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.