From: S Sebinraj <s.sebinraj@intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
intel-xe@lists.freedesktop.org
Cc: jeevaka.badrappan@intel.com, S Sebinraj <s.sebinraj@intel.com>
Subject: [PATCH v4 0/2] drm: Add GPU frequency tracepoint
Date: Wed, 17 Sep 2025 14:11:33 +0530 [thread overview]
Message-ID: <20250917084135.2049550-1-s.sebinraj@intel.com> (raw)
Add a GPU frequency tracepoint at the DRM subsystem level.
Integrates with the Xe PMU to provide frequency tracing.
The tracepoint is exposed at:
/sys/kernel/debug/tracing/events/power/gpu_frequency
Format: {unsigned int state, unsigned int gpu_id}
- state: GPU frequency in KHz
- gpu_id: GPU clock domain identifier
S Sebinraj (2):
drm: Add GPU frequency tracepoint at DRM level
drm/xe: Add DRM GPU frequency tracepoint to Xe
drivers/gpu/drm/Kconfig | 11 ++++++
drivers/gpu/drm/Makefile | 1 +
drivers/gpu/drm/drm_gpu_frequency_trace.c | 16 ++++++++
drivers/gpu/drm/xe/xe_gpu_freq_trace.h | 14 +++++++
drivers/gpu/drm/xe/xe_pmu.c | 26 ++++++++++++-
drivers/gpu/drm/xe/xe_pmu_types.h | 4 ++
include/drm/drm_gpu_frequency_trace.h | 47 +++++++++++++++++++++++
7 files changed, 117 insertions(+), 2 deletions(-)
create mode 100644 drivers/gpu/drm/drm_gpu_frequency_trace.c
create mode 100644 drivers/gpu/drm/xe/xe_gpu_freq_trace.h
create mode 100644 include/drm/drm_gpu_frequency_trace.h
--
2.34.1
next reply other threads:[~2025-09-17 8:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 8:41 S Sebinraj [this message]
2025-09-17 8:41 ` [PATCH v4 1/2] drm: Add GPU frequency tracepoint at DRM level S Sebinraj
2025-09-17 9:17 ` Tvrtko Ursulin
2025-09-17 8:41 ` [PATCH v4 2/2] drm/xe: Add DRM GPU frequency tracepoint to Xe S Sebinraj
2025-09-17 9:19 ` Tvrtko Ursulin
2025-09-17 8:56 ` ✗ CI.checkpatch: warning for drm: Add GPU frequency tracepoint (rev3) Patchwork
2025-09-17 8:57 ` ✓ CI.KUnit: success " Patchwork
2025-09-17 9:43 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-17 10:54 ` ✗ 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=20250917084135.2049550-1-s.sebinraj@intel.com \
--to=s.sebinraj@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jeevaka.badrappan@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