From: Ian Rogers <irogers@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
James Clark <james.clark@linaro.org>,
Weilin Wang <weilin.wang@intel.com>,
Dominique Martinet <asmadeus@codewreck.org>,
Thomas Richter <tmricht@linux.ibm.com>,
Junhao He <hejunhao3@huawei.com>,
Jean-Philippe Romain <jean-philippe.romain@foss.st.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org
Subject: [PATCH v2 0/4] Add support for a DRM tool like PMU
Date: Tue, 25 Mar 2025 20:50:41 -0700 [thread overview]
Message-ID: <20250326035045.129440-1-irogers@google.com> (raw)
DRM clients expose information through usage stats as documented in
Documentation/gpu/drm-usage-stats.rst (available online at
https://docs.kernel.org/gpu/drm-usage-stats.html). Add a tool like
PMU, similar to the hwmon PMU, that exposes DRM information.
v2: Add support to only scan hwmon and drm PMUs if the event or PMU
wildcard can match. Add a test as requested by Namhyung. Add file
comments.
v1:
https://lore.kernel.org/lkml/20250211071727.364389-1-irogers@google.com/
Ian Rogers (4):
perf parse-events: Avoid scanning PMUs that can't contain events
perf parse-events: Avoid scanning PMUs that can't match a wildcard
perf drm_pmu: Add a tool like PMU to expose DRM information
perf tests: Add a DRM PMU test
tools/perf/tests/shell/drm_pmu.sh | 77 ++++
tools/perf/util/Build | 1 +
tools/perf/util/drm_pmu.c | 689 ++++++++++++++++++++++++++++++
tools/perf/util/drm_pmu.h | 39 ++
tools/perf/util/evsel.c | 9 +
tools/perf/util/parse-events.c | 30 +-
tools/perf/util/pmu.c | 15 +
tools/perf/util/pmu.h | 4 +-
tools/perf/util/pmus.c | 101 ++++-
tools/perf/util/pmus.h | 2 +
10 files changed, 951 insertions(+), 16 deletions(-)
create mode 100755 tools/perf/tests/shell/drm_pmu.sh
create mode 100644 tools/perf/util/drm_pmu.c
create mode 100644 tools/perf/util/drm_pmu.h
--
2.49.0.395.g12beb8f557-goog
next reply other threads:[~2025-03-26 3:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 3:50 Ian Rogers [this message]
2025-03-26 3:50 ` [PATCH v2 1/4] perf parse-events: Avoid scanning PMUs that can't contain events Ian Rogers
2025-03-26 3:50 ` [PATCH v2 2/4] perf parse-events: Avoid scanning PMUs that can't match a wildcard Ian Rogers
2025-03-26 3:50 ` [PATCH v2 3/4] perf drm_pmu: Add a tool like PMU to expose DRM information Ian Rogers
2025-03-26 3:50 ` [PATCH v2 4/4] perf tests: Add a DRM PMU test Ian Rogers
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=20250326035045.129440-1-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=asmadeus@codewreck.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hejunhao3@huawei.com \
--cc=james.clark@linaro.org \
--cc=jean-philippe.romain@foss.st.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tmricht@linux.ibm.com \
--cc=weilin.wang@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.