From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 0/7] Add MTL PMU support for multi-gt
Date: Wed, 29 Mar 2023 17:40:54 -0700 [thread overview]
Message-ID: <20230330004103.1295413-1-umesh.nerlige.ramappa@intel.com> (raw)
With MTL, frequency and rc6 counters are specific to a gt. Export these
counters via gt-specific events to the user space.
Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Test-with: 20230330003656.1294873-1-umesh.nerlige.ramappa@intel.com
Tvrtko Ursulin (6):
drm/i915/pmu: Support PMU for all engines
drm/i915/pmu: Skip sampling engines with no enabled counters
drm/i915/pmu: Transform PMU parking code to be GT based
drm/i915/pmu: Add reference counting to the sampling timer
drm/i915/pmu: Prepare for multi-tile non-engine counters
drm/i915/pmu: Export counters from all tiles
Umesh Nerlige Ramappa (3):
drm/i915/pmu: Use a helper to convert to MHz
drm/i915/pmu: Split reading engine and other events into helpers
drm/i915/pmu: Enable legacy PMU events for MTL
drivers/gpu/drm/i915/gt/intel_gt_pm.c | 4 +-
drivers/gpu/drm/i915/i915_pmu.c | 464 ++++++++++++++++++++------
drivers/gpu/drm/i915/i915_pmu.h | 22 +-
include/uapi/drm/i915_drm.h | 22 +-
4 files changed, 394 insertions(+), 118 deletions(-)
--
2.36.1
next reply other threads:[~2023-03-30 0:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 0:40 Umesh Nerlige Ramappa [this message]
2023-03-30 0:40 ` [Intel-gfx] [PATCH 1/9] drm/i915/pmu: Support PMU for all engines Umesh Nerlige Ramappa
2023-03-30 12:27 ` Tvrtko Ursulin
2023-03-30 0:40 ` [Intel-gfx] [PATCH 2/9] drm/i915/pmu: Skip sampling engines with no enabled counters Umesh Nerlige Ramappa
2023-03-30 0:40 ` [Intel-gfx] [PATCH 3/9] drm/i915/pmu: Transform PMU parking code to be GT based Umesh Nerlige Ramappa
2023-03-30 0:40 ` [Intel-gfx] [PATCH 4/9] drm/i915/pmu: Add reference counting to the sampling timer Umesh Nerlige Ramappa
2023-03-30 0:40 ` [Intel-gfx] [PATCH 5/9] drm/i915/pmu: Prepare for multi-tile non-engine counters Umesh Nerlige Ramappa
2023-03-30 12:39 ` Tvrtko Ursulin
2023-03-30 22:28 ` Dixit, Ashutosh
2023-03-31 8:22 ` Tvrtko Ursulin
2023-03-30 0:41 ` [Intel-gfx] [PATCH 6/9] drm/i915/pmu: Export counters from all tiles Umesh Nerlige Ramappa
2023-03-30 13:01 ` Tvrtko Ursulin
2023-03-30 17:33 ` Umesh Nerlige Ramappa
2023-03-31 8:57 ` Tvrtko Ursulin
2023-03-30 0:41 ` [Intel-gfx] [PATCH 7/9] drm/i915/pmu: Use a helper to convert to MHz Umesh Nerlige Ramappa
2023-03-30 13:13 ` Tvrtko Ursulin
2023-03-30 0:41 ` [Intel-gfx] [PATCH 8/9] drm/i915/pmu: Split reading engine and other events into helpers Umesh Nerlige Ramappa
2023-03-30 13:26 ` Tvrtko Ursulin
2023-03-30 0:41 ` [Intel-gfx] [PATCH 9/9] drm/i915/pmu: Enable legacy PMU events for MTL Umesh Nerlige Ramappa
2023-03-30 13:38 ` Tvrtko Ursulin
2023-03-30 18:31 ` Umesh Nerlige Ramappa
2023-03-31 13:02 ` Tvrtko Ursulin
2023-04-20 20:12 ` Umesh Nerlige Ramappa
2023-04-03 19:16 ` Umesh Nerlige Ramappa
2023-03-30 1:37 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Add MTL PMU support for multi-gt Patchwork
2023-03-30 1:37 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-03-30 1:46 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-03-30 19:50 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20230330004103.1295413-1-umesh.nerlige.ramappa@intel.com \
--to=umesh.nerlige.ramappa@intel.com \
--cc=intel-gfx@lists.freedesktop.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