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>,
James Clark <james.clark@linaro.org>,
Ze Gao <zegao2021@gmail.com>,
Weilin Wang <weilin.wang@intel.com>,
Jean-Philippe Romain <jean-philippe.romain@foss.st.com>,
Junhao He <hejunhao3@huawei.com>,
Yicong Yang <yangyicong@hisilicon.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/5] perf hwmon related improvements
Date: Wed, 22 Jan 2025 23:46:54 -0800 [thread overview]
Message-ID: <20250123074659.698123-1-irogers@google.com> (raw)
Try to do less scanning of files/directories with or without hwmon
PMUs. Don't merge all events with the same name, only merge those on
the same PMU ignoring suffix. Tidy PMU name matching to distinguish no
suffix or wildcard matching. Refactor uniquification so the evsels
with the same name as other evsels in the evlist are uniquified.
v2: Rename ignore suffix PMU name matching that is really a
wildcard/prefix match. Use a proper ignore suffix when not merging
counters purely on name.
Ian Rogers (5):
perf evsel: Reduce scanning core PMUs in is_hybrid
perf pmus: Restructure pmu_read_sysfs to scan fewer PMUs
perf pmu: Rename name matching for no suffix or wildcard variants
perf stat: Don't merge counters purely on name
perf stat: Changes to event name uniquification
tools/perf/pmu-events/empty-pmu-events.c | 8 +-
tools/perf/pmu-events/jevents.py | 8 +-
tools/perf/tests/pmu.c | 85 ++++----
tools/perf/util/evsel.c | 4 +-
tools/perf/util/evsel.h | 1 +
tools/perf/util/parse-events.c | 2 +-
tools/perf/util/pmu.c | 252 ++++++++++++++++-------
tools/perf/util/pmu.h | 7 +-
tools/perf/util/pmus.c | 144 ++++++++-----
tools/perf/util/stat-display.c | 111 +++++++---
tools/perf/util/stat.c | 13 +-
11 files changed, 418 insertions(+), 217 deletions(-)
--
2.48.1.262.g85cc9f2d1e-goog
next reply other threads:[~2025-01-23 7:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 7:46 Ian Rogers [this message]
2025-01-23 7:46 ` [PATCH v2 1/5] perf evsel: Reduce scanning core PMUs in is_hybrid Ian Rogers
2025-01-23 7:46 ` [PATCH v2 2/5] perf pmus: Restructure pmu_read_sysfs to scan fewer PMUs Ian Rogers
2025-01-30 19:24 ` Liang, Kan
2025-02-01 7:26 ` Ian Rogers
2025-01-23 7:46 ` [PATCH v2 3/5] perf pmu: Rename name matching for no suffix or wildcard variants Ian Rogers
2025-01-30 19:29 ` Liang, Kan
2025-02-01 7:30 ` Ian Rogers
2025-01-23 7:46 ` [PATCH v2 4/5] perf stat: Don't merge counters purely on name Ian Rogers
2025-01-23 7:46 ` [PATCH v2 5/5] perf stat: Changes to event name uniquification Ian Rogers
2025-01-30 4:29 ` [PATCH v2 0/5] perf hwmon related improvements 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=20250123074659.698123-1-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--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=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=weilin.wang@intel.com \
--cc=yangyicong@hisilicon.com \
--cc=zegao2021@gmail.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