From: Hang Zhengyang <hang.zhengyang1010@gmail.com>
To: Chun-Tse Shao <ctshao@google.com>
Cc: 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>,
James Clark <james.clark@linaro.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7] perf stat: Include PMU name and split uncore events per PMU in metric-only JSON output
Date: Tue, 10 Nov 2026 11:22:38 +0800 [thread overview]
Message-ID: <20261110032240.3080302-1-hang.zhengyang1010@gmail.com> (raw)
In-Reply-To: <20261030192537.3079368-1-ctshao@google.com>
On Fri, 30 Oct 2026 12:25:37 -0700, Chun-Tse Shao wrote:
> When running `perf stat` with `-A` (--no-aggr) and `--metric-only` in
> JSON output mode (`-j`), [...]
Tested on AMD Zen 3 on top of perf-tools-next 13a8d580433a. With
'-M l3_cache,data_fabric,iotlb -a -A --metric-only -j' the metrics are
now on separate lines labeled amd_l3, amd_df and amd_iommu_0. STD, CSV
and aggregated JSON output are unchanged, and the stat linters pass.
Tested-by: Hang Zhengyang <hang.zhengyang1010@gmail.com>
Two changes the changelog doesn't mention:
- Without -M, 'perf stat -a -A --metric-only -j' now prints two lines
per CPU; the first is labeled "pmu" : "software".
- Plain 'perf stat -a -A -j' gets the "pmu" key too.
Are those intended?
(Tested with the help of an AI assistant; I checked the results.)
prev parent reply other threads:[~2026-11-10 3:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 19:25 Chun-Tse Shao
2026-11-10 3:22 ` Hang Zhengyang [this message]
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=20261110032240.3080302-1-hang.zhengyang1010@gmail.com \
--to=hang.zhengyang1010@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ctshao@google.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--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 \
/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
all inboxes | Powered by JetHome®