[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aYx1V443vpL8o7Pv@x1>
Date: Wed, 11 Feb 2026 09:25:59 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Dmitrii Dolgov <9erthalion6@...il.com>,
Adrian Hunter <adrian.hunter@...el.com>,
Ian Rogers <irogers@...gle.com>,
James Clark <james.clark@...aro.org>, Jiri Olsa <jolsa@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-perf-users@...r.kernel.org
Subject: Re: [PATCH 1/1] perf test code_with_type.sh: Skip test if rust
wasn't available at build time
On Mon, Feb 09, 2026 at 05:24:03PM -0800, Namhyung Kim wrote:
> On Mon, Feb 09, 2026 at 03:48:27PM -0300, Arnaldo Carvalho de Melo wrote:
> > $ perf test 'perf data type profiling tests'
> > 83: perf data type profiling tests : Skip
> > $ perf test -vv 'perf data type profiling tests'
> > 83: perf data type profiling tests:
> > --- start ---
> > test child forked, pid 977213
> > Skip: code_with_type workload not built in 'perf test'
> > ---- end(-2) ----
> > 83: perf data type profiling tests : Skip
> > $
> >
> > Cc: Dmitrii Dolgov <9erthalion6@...il.com>
> > Signed-off-by: Arnaldo Carvalho de Melo <acme@...hat.com>
> > ---
> > tools/perf/tests/shell/data_type_profiling.sh | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/tools/perf/tests/shell/data_type_profiling.sh b/tools/perf/tests/shell/data_type_profiling.sh
> > index a230f5d4c42c3e6a..3ef72a10850d0734 100755
> > --- a/tools/perf/tests/shell/data_type_profiling.sh
> > +++ b/tools/perf/tests/shell/data_type_profiling.sh
> > @@ -4,6 +4,11 @@
> >
> > set -e
> >
> > +if ! perf test --list-workloads | grep -qw code_with_type ; then
>
> It could be 'perf check feature -q rust'.
Right, better, more compact and using something that was designed for
that...
> But IIUC this test also covers C code. We may want to skip Rust parts
> only.
I'll cook up a patch implementing your suggestions.
- Arnaldo
> Thanks,
> Namhyung
>
>
> > + echo "Skip: code_with_type workload not built in 'perf test'"
> > + exit 2
> > +fi
> > +
> > # The logic below follows the same line as the annotate test, but looks for a
> > # data type profiling manifestation
> >
> > --
> > 2.53.0
> >
Powered by blists - more mailing lists