From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Ravi Bangoria <ravi.bangoria@amd.com>,
Weilin Wang <weilin.wang@intel.com>,
Yoshihiro Furudera <fj5100bi@fujitsu.com>,
James Clark <james.clark@linaro.org>,
Athira Jajeev <atrajeev@linux.vnet.ibm.com>,
Howard Chu <howardchu95@gmail.com>,
Oliver Upton <oliver.upton@linux.dev>,
Changbin Du <changbin.du@huawei.com>,
Ze Gao <zegao2021@gmail.com>, Junhao He <hejunhao3@huawei.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v6 0/5] Hwmon PMUs
Date: Wed, 23 Oct 2024 20:06:43 -0700 [thread overview]
Message-ID: <Zxm5w6wXLxpbERZx@google.com> (raw)
In-Reply-To: <20241022180623.463131-1-irogers@google.com>
Hi Ian,
On Tue, Oct 22, 2024 at 11:06:18AM -0700, Ian Rogers wrote:
> Following the convention of the tool PMU, create a hwmon PMU that
> exposes hwmon data for reading. For example, the following shows
> reading the CPU temperature and 2 fan speeds alongside the uncore
> frequency:
> ```
> $ perf stat -e temp_cpu,fan1,hwmon_thinkpad/fan2/,tool/num_cpus_online/ -M UNCORE_FREQ -I 1000
> 1.001153138 52.00 'C temp_cpu
> 1.001153138 2,588 rpm fan1
> 1.001153138 2,482 rpm hwmon_thinkpad/fan2/
> 1.001153138 8 tool/num_cpus_online/
> 1.001153138 1,077,101,397 UNC_CLOCK.SOCKET # 1.08 UNCORE_FREQ
> 1.001153138 1,012,773,595 duration_time
> ...
> ```
>
> Additional data on the hwmon events is in perf list:
> ```
> $ perf list
> ...
> hwmon:
> ...
> temp_core_0 OR temp2
> [Temperature in unit coretemp named Core 0. crit=100'C,max=100'C crit_alarm=0'C. Unit:
> hwmon_coretemp]
> ...
> ```
>
> v6: Add string.h #include for issue reported by kernel test robot.
> v5: Fix asan issue in parse_hwmon_filename caught by a TMA metric.
> v4: Drop merged patches 1 to 10. Separate adding the hwmon_pmu from
> the update to perf_pmu to use it. Try to make source of literal
> strings clearer via named #defines. Fix a number of GCC warnings.
> v3: Rebase, add Namhyung's acked-by to patches 1 to 10.
> v2: Address Namhyung's review feedback. Rebase dropping 4 patches
> applied by Arnaldo, fix build breakage reported by Arnaldo.
>
> Ian Rogers (5):
> tools api io: Ensure line_len_out is always initialized
> perf hwmon_pmu: Add a tool PMU exposing events from hwmon in sysfs
> perf pmu: Add calls enabling the hwmon_pmu
> perf test: Add hwmon "PMU" test
> perf docs: Document tool and hwmon events
I think the patch 2 can be easily splitted into core and other parts
like dealing with aliases and units. I believe it'd be helpful for
others (like me) to understand how it works.
Please take a look at 'perf/hwmon-pmu' branch in:
https://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
Thanks,
Namhyung
>
> tools/lib/api/io.h | 1 +
> tools/perf/Documentation/perf-list.txt | 15 +
> tools/perf/tests/Build | 1 +
> tools/perf/tests/builtin-test.c | 1 +
> tools/perf/tests/hwmon_pmu.c | 243 ++++++++
> tools/perf/tests/tests.h | 1 +
> tools/perf/util/Build | 1 +
> tools/perf/util/evsel.c | 9 +
> tools/perf/util/hwmon_pmu.c | 821 +++++++++++++++++++++++++
> tools/perf/util/hwmon_pmu.h | 154 +++++
> tools/perf/util/pmu.c | 20 +
> tools/perf/util/pmu.h | 2 +
> tools/perf/util/pmus.c | 9 +
> tools/perf/util/pmus.h | 3 +
> 14 files changed, 1281 insertions(+)
> create mode 100644 tools/perf/tests/hwmon_pmu.c
> create mode 100644 tools/perf/util/hwmon_pmu.c
> create mode 100644 tools/perf/util/hwmon_pmu.h
>
> --
> 2.47.0.163.g1226f6d8fa-goog
>
next prev parent reply other threads:[~2024-10-24 3:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 18:06 [PATCH v6 0/5] Hwmon PMUs Ian Rogers
2024-10-22 18:06 ` [PATCH v6 1/5] tools api io: Ensure line_len_out is always initialized Ian Rogers
2024-10-22 18:06 ` [PATCH v6 2/5] perf hwmon_pmu: Add a tool PMU exposing events from hwmon in sysfs Ian Rogers
2024-10-22 18:06 ` [PATCH v6 3/5] perf pmu: Add calls enabling the hwmon_pmu Ian Rogers
2024-10-22 18:06 ` [PATCH v6 4/5] perf test: Add hwmon "PMU" test Ian Rogers
2024-10-22 18:06 ` [PATCH v6 5/5] perf docs: Document tool and hwmon events Ian Rogers
2024-10-24 3:06 ` Namhyung Kim [this message]
2024-10-24 7:07 ` [PATCH v6 0/5] Hwmon PMUs Ian Rogers
2024-10-24 16:40 ` Namhyung Kim
2024-10-25 1:33 ` Ian Rogers
2024-10-25 17:30 ` Namhyung Kim
2024-10-25 18:26 ` Ian Rogers
2024-10-25 21:01 ` Arnaldo Carvalho de Melo
2024-10-25 23:07 ` Ian Rogers
2024-10-26 17:16 ` Namhyung Kim
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=Zxm5w6wXLxpbERZx@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=changbin.du@huawei.com \
--cc=fj5100bi@fujitsu.com \
--cc=hejunhao3@huawei.com \
--cc=howardchu95@gmail.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--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=oliver.upton@linux.dev \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.com \
--cc=weilin.wang@intel.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