From: Namhyung Kim <namhyung@kernel.org>
To: Thomas Richter <tmricht@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linux-perf-users@vger.kernel.org, acme@kernel.org,
agordeev@linux.ibm.com, gor@linux.ibm.com,
sumanthk@linux.ibm.com, hca@linux.ibm.com, japo@linux.ibm.com
Subject: Re: [PATCH] perf test: Skip perf data type profiling tests for s390
Date: Mon, 30 Mar 2026 23:58:52 -0700 [thread overview]
Message-ID: <actwrDEWZpcdgYzN@google.com> (raw)
In-Reply-To: <20260327123541.1756317-1-tmricht@linux.ibm.com>
On Fri, Mar 27, 2026 at 01:35:41PM +0100, Thomas Richter wrote:
> Test case 'perf data type profiling tests' fails on s390 with this
> error:
>
> # ./perf mem record -- ./perf test -w code_with_type
> failed: no PMU supports the memory events
> # echo $?
> 255
> #
>
> because s390 does not support memory events at all. According to the
> man page, perf annotate --code-with-type only works with memory
> instructions only. As command 'perf mem record ...' is not supported
> on s390, skip this test for s390.
>
> Output before:
> # ./perf test 'perf data type profiling tests'
> 77: perf data type profiling tests : FAILED!
>
> Output after:
> # ./perf test 'perf data type profiling tests'
> 77: perf data type profiling tests : Skip
>
> Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Dmitrii Dolgov <9erthalion6@gmail.com>
> Acked-by: Sumanth Korikkar <sumanthk@linux.ibm.com>
> Tested-by: Jan Polensky <japo@linux.ibm.com>
> ---
> tools/perf/tests/shell/data_type_profiling.sh | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/tools/perf/tests/shell/data_type_profiling.sh b/tools/perf/tests/shell/data_type_profiling.sh
> index 2a7f8f7c42d0..d9393be6249e 100755
> --- a/tools/perf/tests/shell/data_type_profiling.sh
> +++ b/tools/perf/tests/shell/data_type_profiling.sh
> @@ -35,6 +35,12 @@ test_basic_annotate() {
>
> echo "${mode} ${runtime} perf annotate test"
>
> + case "$(uname -m)" in
> + "s390x")
> + echo "Skip: 'perf mem record' not supported"
> + err=2
> + return ;;
> + esac
Then I think it should be general like checking the error code after
running `perf mem record` first instead of looking at machine types.
Thanks,
Namhyung
> case "x${runtime}" in
> "xRust")
> if ! perf check feature -q rust
> --
> 2.53.0
>
prev parent reply other threads:[~2026-03-31 6:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 12:35 [PATCH] perf test: Skip perf data type profiling tests for s390 Thomas Richter
2026-03-31 6:58 ` Namhyung Kim [this message]
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=actwrDEWZpcdgYzN@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=japo@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sumanthk@linux.ibm.com \
--cc=tmricht@linux.ibm.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 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.