From: "Liang, Kan" <kan.liang@linux.intel.com>
To: James Clark <james.clark@linaro.org>,
irogers@google.com, linux-perf-users@vger.kernel.org,
ak@linux.intel.com, namhyung@kernel.org
Cc: John Garry <john.g.garry@oracle.com>,
Will Deacon <will@kernel.org>, Mike Leach <mike.leach@linaro.org>,
Leo Yan <leo.yan@linux.dev>,
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>,
Weilin Wang <weilin.wang@intel.com>,
Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
Dominique Martinet <asmadeus@codewreck.org>,
Yang Jihong <yangjihong@bytedance.com>,
Colin Ian King <colin.i.king@gmail.com>,
Howard Chu <howardchu95@gmail.com>, Ze Gao <zegao2021@gmail.com>,
Jing Zhang <renyu.zj@linux.alibaba.com>,
Sun Haiyong <sunhaiyong@loongson.cn>,
Yicong Yang <yangyicong@hisilicon.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/7] Event parsing fixes
Date: Thu, 5 Sep 2024 14:20:54 -0400 [thread overview]
Message-ID: <8133d432-7674-4d07-bbb5-4131fe5d474e@linux.intel.com> (raw)
In-Reply-To: <20240903102005.78049-1-james.clark@linaro.org>
On 2024-09-03 6:19 a.m., James Clark wrote:
> I rebased this one and made some other fixes so that I could test it,
> so I thought I'd repost it here in case it's helpful. I also added a
> new test.
>
> But for the testing it all looks ok.
>
> There is one small difference where it now hides _all_ default
> <not supported> events, when previously it would only hide some
> selected subset of events like "stalled-cycles-frontend". I think
> this is now more consistent across platforms because, for example,
> Apple M only has cycles and instructions, and the rest of the
> default events would always show as <not supported> there.
>
> Tested on Raptor Lake, Kaby Lake, Juno, N1, Ampere (with the DSU
> cycles PMU) and I also faked an Apple M on Juno.
>
The tui mode in perf report is broken on Intel hybrid machine.
$perf record -e cycles,instructions sleep 1
$perf report
Without the patch set, in the tui mode,
Available samples
7 cpu_atom/cycles/
◆
0 cpu_core/cycles/
▒
7 cpu_atom/instructions/
▒
0 cpu_core/instructions/
▒
0 dummy:u
After applying the patch set,
Available samples
7 /cycles/
◆
0 /cycles/
▒
7 /instructions/
▒
0 /instructions/
▒
0 dummy:u
It looks something wrong with the uniquify_event_name().
Thanks,
Kan
> Changes since v5:
> * Test on x86 non hybrid
> * Assume 1 PMU in the test when no PMUs expose /cpus file
>
> Changes since v4:
>
> * Hide all <not supported> default events when not verbose
> * Remove previous note about <not supported> behavior from the cover
> letter and replace it with a new note about the new behavior
>
> Changes since v3:
>
> * Rebase onto perf-tools-next 6236ebe07
> * Fix Intel TPEBS counting mode test
> * Fix arm-spe build
> * Add support for DT devices in stat test
> * Add a new test for hybrid perf stat default arguments
>
> Ian Rogers (5):
> perf evsel: Add alternate_hw_config and use in evsel__match
> perf stat: Uniquify event name improvements
> perf stat: Remove evlist__add_default_attrs use strings
> perf evsel x86: Make evsel__has_perf_metrics work for legacy events
> perf evsel: Remove pmu_name
>
> James Clark (2):
> perf test: Make stat test work on DT devices
> perf test: Add a test for default perf stat command
>
> tools/perf/arch/arm64/util/arm-spe.c | 4 +-
> tools/perf/arch/x86/util/evlist.c | 74 +----
> tools/perf/arch/x86/util/evsel.c | 35 ++-
> tools/perf/builtin-diff.c | 6 +-
> tools/perf/builtin-stat.c | 291 +++++++-----------
> tools/perf/tests/parse-events.c | 2 +-
> tools/perf/tests/shell/stat.sh | 37 ++-
> .../perf/tests/shell/test_stat_intel_tpebs.sh | 11 +-
> tools/perf/util/evlist.c | 46 +--
> tools/perf/util/evlist.h | 12 -
> tools/perf/util/evsel.c | 28 +-
> tools/perf/util/evsel.h | 22 +-
> tools/perf/util/metricgroup.c | 4 +-
> tools/perf/util/parse-events.c | 58 ++--
> tools/perf/util/parse-events.h | 8 +-
> tools/perf/util/parse-events.y | 2 +-
> tools/perf/util/pmu.c | 6 +-
> tools/perf/util/pmu.h | 2 +-
> tools/perf/util/stat-display.c | 109 +++++--
> tools/perf/util/stat-shadow.c | 14 +-
> tools/perf/util/stat.c | 2 +-
> 21 files changed, 360 insertions(+), 413 deletions(-)
>
next prev parent reply other threads:[~2024-09-05 18:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 10:19 [PATCH v6 0/7] Event parsing fixes James Clark
2024-09-03 10:19 ` [PATCH v6 1/7] perf evsel: Add alternate_hw_config and use in evsel__match James Clark
2024-09-03 10:19 ` [PATCH v6 2/7] perf stat: Uniquify event name improvements James Clark
2024-09-03 10:19 ` [PATCH v6 3/7] perf stat: Remove evlist__add_default_attrs use strings James Clark
2024-09-03 10:19 ` [PATCH v6 4/7] perf evsel x86: Make evsel__has_perf_metrics work for legacy events James Clark
2024-09-03 10:19 ` [PATCH v6 5/7] perf evsel: Remove pmu_name James Clark
2024-09-03 10:19 ` [PATCH v6 6/7] perf test: Make stat test work on DT devices James Clark
2024-09-03 10:19 ` [PATCH v6 7/7] perf test: Add a test for default perf stat command James Clark
2024-09-05 4:09 ` [PATCH v6 0/7] Event parsing fixes Namhyung Kim
2024-09-05 18:20 ` Liang, Kan [this message]
2024-09-10 9:27 ` James Clark
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=8133d432-7674-4d07-bbb5-4131fe5d474e@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=asmadeus@codewreck.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=colin.i.king@gmail.com \
--cc=howardchu95@gmail.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=renyu.zj@linux.alibaba.com \
--cc=sunhaiyong@loongson.cn \
--cc=weilin.wang@intel.com \
--cc=will@kernel.org \
--cc=yangjihong@bytedance.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;
as well as URLs for NNTP newsgroup(s).