From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Chun-Tse Shao <ctshao@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
"Dr. David Alan Gilbert" <linux@treblig.org>,
Howard Chu <howardchu95@gmail.com>,
Ian Rogers <irogers@google.com>, Ingo Molnar <mingo@redhat.com>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
Levi Yun <yeoreum.yun@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Weilin Wang <weilin.wang@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 1/1 v6.16] perf test event_uniquifying: Skip test on platforms without 'clockticks' events
Date: Fri, 6 Jun 2025 17:18:04 -0300 [thread overview]
Message-ID: <aENM_KGb-x14pHRX@x1> (raw)
In-Reply-To: <aEMqwmCmbyAlb1Y1@google.com>
On Fri, Jun 06, 2025 at 10:52:02AM -0700, Namhyung Kim wrote:
> On Thu, Jun 05, 2025 at 04:22:40PM -0300, Arnaldo Carvalho de Melo wrote:
> > I'll add this to perf-tools for v6.16, please check.
>
> Plesae see
>
> https://lore.kernel.org/linux-perf-users/20250521224513.1104129-1-ctshao@google.com/
Oh, great, I'll drop my fix and get that one instead.
- Arnaldo
> Thanks,
> Namhyung
>
> > ---
> >
> > This test assumes the 'clockticks' event is generally available, which
> > isn't the case, for instance, on AMD systems such as:
> >
> > root@number:~# grep -m1 "model name" /proc/cpuinfo
> > model name : AMD Ryzen 9 9950X3D 16-Core Processor
> > root@number:~# perf list clockticks
> >
> > List of pre-defined events (to be used in -e or -M):
> >
> > root@number:~#
> >
> > So skip this test when 'clockticks' isn't available.
> >
> > This should be improved to find other events that are available in
> > multiple PMUs so that the intent of the test is achieved in more
> > platforms.
> >
> > Fixes: cb422594d62066a5 ("perf test: Add stat uniquifying test")
> > Cc: Adrian Hunter <adrian.hunter@intel.com>
> > Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> > Cc: Andi Kleen <ak@linux.intel.com>
> > Cc: Chun-Tse Shao <ctshao@google.com>
> > Cc: Dr. David Alan Gilbert <linux@treblig.org>
> > Cc: Howard Chu <howardchu95@gmail.com>
> > Cc: Ian Rogers <irogers@google.com>
> > Cc: Ingo Molnar <mingo@redhat.com>
> > Cc: James Clark <james.clark@linaro.org>
> > Cc: Jiri Olsa <jolsa@kernel.org>
> > Cc: Kan Liang <kan.liang@linux.intel.com>
> > Cc: Levi Yun <yeoreum.yun@arm.com>
> > Cc: Mark Rutland <mark.rutland@arm.com>
> > Cc: Namhyung Kim <namhyung@kernel.org>
> > Cc: Peter Zijlstra <peterz@infradead.org>
> > Cc: Weilin Wang <weilin.wang@intel.com>
> > Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> > ---
> > tools/perf/tests/shell/stat+event_uniquifying.sh | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/tools/perf/tests/shell/stat+event_uniquifying.sh b/tools/perf/tests/shell/stat+event_uniquifying.sh
> > index 5ec35c52b7d9651e..20498b6eadb57702 100755
> > --- a/tools/perf/tests/shell/stat+event_uniquifying.sh
> > +++ b/tools/perf/tests/shell/stat+event_uniquifying.sh
> > @@ -49,6 +49,12 @@ test_event_uniquifying() {
> > uniquified_event_array+=("${uniquified_event}")
> > done < <(${perf_tool} list -v ${event} | grep "\[Kernel PMU event\]")
> >
> > + if [ ${#uniquified_event_array[@]} -eq 0 ]; then
> > + echo "'clocktick' event not available on this machine"
> > + err=2
> > + return
> > + fi
> > +
> > perf_command="${perf_tool} stat -e $event -A -o ${stat_output} -- true"
> > $perf_command
> >
> > --
> > 2.49.0
> >
next prev parent reply other threads:[~2025-06-06 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 19:22 [PATCH 1/1 v6.16] perf test event_uniquifying: Skip test on platforms without 'clockticks' events Arnaldo Carvalho de Melo
2025-06-06 17:52 ` Namhyung Kim
2025-06-06 20:18 ` Arnaldo Carvalho de Melo [this message]
2025-06-06 20:25 ` Arnaldo Carvalho de Melo
2025-06-07 2:55 ` Chun-Tse Shao
2025-06-09 15:18 ` Arnaldo Carvalho de Melo
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=aENM_KGb-x14pHRX@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ctshao@google.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=linux@treblig.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=weilin.wang@intel.com \
--cc=yeoreum.yun@arm.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