From: Heiko Carstens <hca@linux.ibm.com>
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,
namhyung@kernel.org, agordeev@linux.ibm.com, gor@linux.ibm.com,
sumanthk@linux.ibm.com
Subject: Re: [PATCH] perf/tests: Fix tests 84 and 86 Add --metric-only on s390
Date: Thu, 17 Apr 2025 13:52:04 +0200 [thread overview]
Message-ID: <20250417115204.12521Ef5-hca@linux.ibm.com> (raw)
In-Reply-To: <20250415134553.3089594-1-tmricht@linux.ibm.com>
On Tue, Apr 15, 2025 at 03:45:53PM +0200, Thomas Richter wrote:
> On s390x z/VM machines the CPU Measurement Facility is not available.
> Events cycles and instructions do not exist.
> Running above tests on s390 z/VM always fails with this error:
>
> # ./perf test 84 86
> 84: perf stat JSON output linter : FAILED!
> 86: perf stat STD output linter : FAILED!
> #
I would guess this fails also for KVM guests?
> diff --git a/tools/perf/tests/shell/lib/stat_output.sh b/tools/perf/tests/shell/lib/stat_output.sh
> index 4d4aac547f01..a708dedf7d9d 100644
> --- a/tools/perf/tests/shell/lib/stat_output.sh
> +++ b/tools/perf/tests/shell/lib/stat_output.sh
> @@ -151,6 +151,11 @@ check_per_socket()
> check_metric_only()
> {
> echo -n "Checking $1 output: metric only "
> + if [ "$(uname -m)" = "s390x" ] && grep -q z/VM /proc/sysinfo
> + then
> + echo "[Skip] not supported on z/VM"
> + return
> + fi
Wouldn't it be better to test for the availability of the CPU-measurement
counter facility? That is: test if facility number 67 is present in the
facilities field of /proc/cpuinfo.
next prev parent reply other threads:[~2025-04-17 11:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 13:45 [PATCH] perf/tests: Fix tests 84 and 86 Add --metric-only on s390 Thomas Richter
2025-04-17 11:52 ` Heiko Carstens [this message]
2025-04-22 9:30 ` Thomas Richter
-- strict thread matches above, loose matches on Subject: below --
2025-04-24 13:33 Thomas Richter
2025-04-24 17:50 ` 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=20250417115204.12521Ef5-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=acme@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=namhyung@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.