All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Hang Zhengyang <hang.zhengyang1010@gmail.com>,
	Ian Rogers <irogers@google.com>
Cc: Chun-Tse Shao <ctshao@google.com>,
	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>,
	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 22:28:57 -0800	[thread overview]
Message-ID: <avQLKYycwzv68fVf@z2> (raw)
In-Reply-To: <20261110032240.3080302-1-hang.zhengyang1010@gmail.com>

On Tue, Nov 10, 2026 at 11:22:38AM +0800, Hang Zhengyang wrote:
> 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?

I believe it's intended and looks fine.

Ian, are you ok with this?

Thanks,
Na

  reply	other threads:[~2026-11-11  6:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 19:25 [PATCH v7] perf stat: Include PMU name and split uncore events per PMU in metric-only JSON output Chun-Tse Shao
2026-10-30 19:34 ` sashiko-bot
2026-11-10  3:22 ` Hang Zhengyang
2026-11-11  6:28   ` Namhyung Kim [this message]
2026-11-11 18:33     ` Chun-Tse Shao

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=avQLKYycwzv68fVf@z2 \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=ctshao@google.com \
    --cc=hang.zhengyang1010@gmail.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=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 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.