From: Ravi Bangoria <ravi.bangoria@amd.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ian Rogers <irogers@google.com>,
Kan Liang <kan.liang@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org, Leo Yan <leo.yan@arm.com>,
Ravi Bangoria <ravi.bangoria@amd.com>
Subject: Re: [RFC/PATCHSET 00/11] perf mem: Add new output fields for data source (v1)
Date: Thu, 8 May 2025 09:42:41 +0530 [thread overview]
Message-ID: <33984b44-ae3d-4fbd-b918-07289a3f1d8a@amd.com> (raw)
In-Reply-To: <20250430205548.789750-1-namhyung@kernel.org>
Hi Namhyung,
I feel the overall idea is good. Running few simple perf-mem commands
on AMD works fine too. Few general feedback below.
> The name of some new fields are the same as the corresponding sort
> keys (mem, op, snoop) so I had to change the order whether it's
> applied as an output field or a sort key. Maybe it's better to name
> them differently but I couldn't come up with better ideas.
1) These semantic changes of the field name seems counter intuitive
(to me). Example:
-F mem:
Without patch:
$ perf mem report -F overhead,sample,mem --stdio
# Overhead Samples Memory access
39.29% 1 L3 hit
37.50% 21 N/A
23.21% 13 L1 hit
With patch:
$ perf mem report -F overhead,sample,mem --stdio
# Memory
# Overhead Samples Other
100.00% 35 100.0%
-F 'snoop':
Without patch:
$ perf mem report -F overhead,sample,snoop --stdio
# Overhead Samples Snoop
60.71% 34 N/A
39.29% 1 HitM
With patchset:
$ perf mem report -F overhead,sample,snoop --stdio
# --- Snoop ----
# Overhead Samples HitM Other
100.00% 35 39.3% 60.7%
2) It was not intuitive (to me:)) that perf-mem overhead is calculated
using sample->weight by overwriting sample->period. I also don't see
it documented anywhere (or did I miss it?)
perf report:
$ perf report -F overhead,sample,period,dso --stdio
# Overhead Samples Period Shared Object
80.00% 28 2800000 [kernel.kallsyms]
5.71% 2 200000 ld-linux-x86-64.so.2
5.71% 2 200000 libc.so.6
5.71% 2 200000 ls
2.86% 1 100000 libpcre2-8.so.0.11.2
perf mem report:
$ perf mem report -F overhead,sample,period,dso --stdio
# Overhead Samples Period Shared Object
87.50% 28 49 [kernel.kallsyms]
3.57% 2 2 ld-linux-x86-64.so.2
3.57% 2 2 libc.so.6
3.57% 2 2 ls
1.79% 1 1 libpcre2-8.so.0.11.2
3) Similarly, it was not intuitive (again, to me:)) that -F op/snoop/dtlb
percentages are calculated based on sample->weight.
4) I've similar recommended perf-mem command in perf-amd-ibs man page.
Can you please update alternate command there.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/perf/Documentation/perf-amd-ibs.txt?h=v6.15-rc5#n167
Please correct me if I'm missing anything.
Thanks,
Ravi
next prev parent reply other threads:[~2025-05-08 4:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 20:55 Namhyung Kim
2025-04-30 20:55 ` [PATCH 01/11] perf hist: Remove output field from sort-list properly Namhyung Kim
2025-04-30 20:55 ` [PATCH 02/11] perf record: Add --sample-mem-info option Namhyung Kim
2025-04-30 20:55 ` [PATCH 03/11] perf hist: Support multi-line header Namhyung Kim
2025-04-30 20:55 ` [PATCH 04/11] perf hist: Add struct he_mem_stat Namhyung Kim
2025-04-30 20:55 ` [PATCH 05/11] perf hist: Basic support for mem_stat accounting Namhyung Kim
2025-04-30 20:55 ` [PATCH 06/11] perf hist: Implement output fields for mem stats Namhyung Kim
2025-04-30 20:55 ` [PATCH 07/11] perf mem: Add 'op' output field Namhyung Kim
2025-04-30 20:55 ` [PATCH 08/11] perf hist: Hide unused mem stat columns Namhyung Kim
2025-05-02 16:18 ` Arnaldo Carvalho de Melo
2025-05-02 16:27 ` Arnaldo Carvalho de Melo
2025-05-02 18:21 ` Namhyung Kim
2025-04-30 20:55 ` [PATCH 09/11] perf mem: Add 'cache' and 'memory' output fields Namhyung Kim
2025-04-30 20:55 ` [PATCH 10/11] perf mem: Add 'snoop' output field Namhyung Kim
2025-04-30 20:55 ` [PATCH 11/11] perf mem: Add 'dtlb' " Namhyung Kim
2025-05-02 16:30 ` Arnaldo Carvalho de Melo
2025-05-02 18:38 ` Namhyung Kim
2025-05-02 19:21 ` Arnaldo Carvalho de Melo
2025-05-02 20:01 ` Namhyung Kim
2025-05-02 16:00 ` [RFC/PATCHSET 00/11] perf mem: Add new output fields for data source (v1) Arnaldo Carvalho de Melo
2025-05-08 4:12 ` Ravi Bangoria [this message]
2025-05-09 16:17 ` Namhyung Kim
2025-05-12 10:01 ` Ravi Bangoria
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=33984b44-ae3d-4fbd-b918-07289a3f1d8a@amd.com \
--to=ravi.bangoria@amd.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--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®