From: Soham Purkait <soham.purkait@intel.com>
To: intel-xe@lists.freedesktop.org, anshuman.gupta@intel.com,
badal.nilawar@intel.com, karthik.poosa@intel.com,
riana.tauro@intel.com, jonathan.cavitt@intel.com
Cc: lucas.demarchi@intel.com, soham.purkait@intel.com,
ashutosh.dixit@intel.com, jani.nikula@intel.com
Subject: [PATCH v5 0/2] Add debugfs node to expose G-state and pcie link state residency
Date: Fri, 20 Jun 2025 17:33:54 +0530 [thread overview]
Message-ID: <20250620120356.3289744-1-soham.purkait@intel.com> (raw)
This patch exposes G-state and pcie link state residency counter
values through debugfs. The debugfs node "dgfx_pkg_residencies" exposes
G-states counters (G2, G6, G8, G10, ModS) and "dgfx_pcie_link_residencies"
exposes PCIe link states(L0, L1, L1.2) residency counters.
Soham Purkait (2):
drm/xe/regs/xe_pmt: Macros for G-State and pcie link state residency
offset
drm/xe/xe_debugfs: Exposure of G-State and pcie link state residency
counters through debugfs
drivers/gpu/drm/xe/regs/xe_pmt.h | 10 +++++
drivers/gpu/drm/xe/xe_debugfs.c | 71 ++++++++++++++++++++++++++++++++
2 files changed, 81 insertions(+)
--
2.34.1
next reply other threads:[~2025-06-20 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 12:03 Soham Purkait [this message]
2025-06-20 12:03 ` [PATCH v5 1/2] drm/xe/regs/xe_pmt: Macros for G-State and pcie link state residency offset Soham Purkait
2025-06-22 5:57 ` Gupta, Anshuman
2025-06-24 13:10 ` Poosa, Karthik
2025-06-20 12:03 ` [PATCH v5 2/2] drm/xe/xe_debugfs: Exposure of G-State and pcie link state residency counters through debugfs Soham Purkait
2025-06-24 13:01 ` Poosa, Karthik
2025-06-20 12:28 ` ✗ CI.checkpatch: warning for Add debugfs node to expose G-state and pcie link state residency (rev3) Patchwork
2025-06-20 12:29 ` ✓ CI.KUnit: success " Patchwork
2025-06-20 22:52 ` ✗ 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=20250620120356.3289744-1-soham.purkait@intel.com \
--to=soham.purkait@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jonathan.cavitt@intel.com \
--cc=karthik.poosa@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=riana.tauro@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