From: Thomas Richter <tmricht@linux.ibm.com>
To: German Gomez <german.gomez@arm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
acme@kernel.org, irogers@google.com
Cc: svens@linux.ibm.com, gor@linux.ibm.com, sumanthk@linux.ibm.com,
hca@linux.ibm.com
Subject: Re: [PATCH] perf test: Fix test case 81 on s390x
Date: Thu, 28 Apr 2022 17:17:16 +0200 [thread overview]
Message-ID: <4eb9f64c-aabd-8461-27a4-05b2e808e1f0@linux.ibm.com> (raw)
In-Reply-To: <768de4e7-7bf1-62b5-4446-28420c3a82d5@arm.com>
On 4/28/22 15:43, German Gomez wrote:
>
> On 28/04/2022 13:28, Thomas Richter wrote:
>> perf test -F 81 -v fails on s390x on the linux-next branch.
>> The test case is x86 specific can not be executed on s390x.
>> The test case depends on x86 register names such as
>>
>> ... | egrep -q 'available registers: AX BX CX DX ....'
>>
>> Skip this test case on s390x.
>>
>> Output before:
>> # perf test -F 81
>> 81: perf record tests : FAILED!
>> #
>>
>> Output after:
>> # perf test -F 81
>> 81: perf record tests : Skip
>> #
>>
>> Fixes: 24f378e66021 ("perf test: Add basic perf record tests")
>> Cc: Ian Rogers <irogers@google.com>
>> Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
>> ---
>> tools/perf/tests/shell/record.sh | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/tools/perf/tests/shell/record.sh b/tools/perf/tests/shell/record.sh
>> index cd1cf14259b8..d98f4d4a00e1 100755
>> --- a/tools/perf/tests/shell/record.sh
>> +++ b/tools/perf/tests/shell/record.sh
>> @@ -37,6 +37,8 @@ test_register_capture() {
>> echo "Register capture test [Success]"
>> }
>>
>> +# Test for platform support and return TEST_SKIP
>> +[ $(uname -m) = s390x ] && exit 2
>> test_per_thread
>
> The "test_per_thread" might still be valid though, right?
>
Right,
this issue is the perf record -e instructions:u event
which is not supported on all machine types and configurations
we have in our test suite.
Because of the 'set -e' at the beginning, the first perf
command fails and the shell exits with error code.
Since s390x does not support x86 register names anyway, it is easier
to just omit this test case on s390x. At least I thought so.
The alternative would be to add some more tests to check s390x
machine supports instructions:u event and then just to bail
out on the register_capture test function.
Maybe this helps.
> In my case, the register test skips gracefully (arm64).
>
> $ ./perf test 82 -v
> 82: perf record tests :
> --- start ---
> test child forked, pid 54345
> Basic --per-thread mode test
> Basic --per-thread mode test [Success]
> Register capture test
> Register capture test [Skipped missing instruction]
> test child finished with 0
> ---- end ----
> perf record tests: Ok
>
>> test_register_capture
>> exit $err
--
Thomas Richter, Dept 3303, IBM s390 Linux Development, Boeblingen, Germany
--
Vorsitzender des Aufsichtsrats: Gregor Pillen
Geschäftsführung: David Faller
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
prev parent reply other threads:[~2022-04-28 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 12:28 [PATCH] perf test: Fix test case 81 on s390x Thomas Richter
2022-04-28 13:25 ` Arnaldo Carvalho de Melo
2022-04-28 13:43 ` John Garry
2022-04-28 13:43 ` German Gomez
2022-04-28 15:17 ` Thomas Richter [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=4eb9f64c-aabd-8461-27a4-05b2e808e1f0@linux.ibm.com \
--to=tmricht@linux.ibm.com \
--cc=acme@kernel.org \
--cc=german.gomez@arm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sumanthk@linux.ibm.com \
--cc=svens@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox