From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Thomas Richter <tmricht@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
sumanthk@linux.ibm.com, jolsa@redhat.com, svens@linux.ibm.com,
gor@linux.ibm.com, hca@linux.ibm.com
Subject: Re: [PATCH] perf/test: Test case 27 broken on s390 in linux-next
Date: Wed, 17 Nov 2021 14:00:48 +0530 [thread overview]
Message-ID: <d8943b3f-b2d5-8b5c-cbf9-14360a6df2b4@linux.ibm.com> (raw)
In-Reply-To: <YYbYXT5O2KTxLAKC@kernel.org>
On 11/7/21 01:02, Arnaldo Carvalho de Melo wrote:
> Em Wed, Nov 03, 2021 at 04:52:15PM +0100, Thomas Richter escreveu:
>> Commit 10269a2ca2b08c ("perf test sample-parsing: Add endian test for struct branch_flags")
>> broke the test case 27 (Sample parsing) on s390 on linux-next tree:
> Maddy,
>
> Can you please ack this one?
Sorry i missed this completely. My bad. Will check it and will reply.
Maddy
>
> - Arnaldo
>
>> # ./perf test -Fv 27
>> 27: Sample parsing
>> --- start ---
>> parsing failed for sample_type 0x800
>> ---- end ----
>> Sample parsing: FAILED!
>> #
>>
>> The cause of the failure is a wrong #define BS_EXPECTED_BE statement
>> in above commit. Correct this define and the test case runs fine.
>>
>> Output After:
>> # ./perf test -Fv 27
>> 27: Sample parsing :
>> --- start ---
>> ---- end ----
>> Sample parsing: Ok
>> #
>>
>> Fixes: 10269a2ca2b08c ("perf test sample-parsing: Add endian test for struct branch_flags")
>> Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
>> ---
>> tools/perf/tests/sample-parsing.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/tools/perf/tests/sample-parsing.c b/tools/perf/tests/sample-parsing.c
>> index c83a11514129..9c7af55b74db 100644
>> --- a/tools/perf/tests/sample-parsing.c
>> +++ b/tools/perf/tests/sample-parsing.c
>> @@ -36,7 +36,7 @@
>> * These are based on the input value (213) specified
>> * in branch_stack variable.
>> */
>> -#define BS_EXPECTED_BE 0xa00d000000000000
>> +#define BS_EXPECTED_BE 0xa000d00000000000
>> #define BS_EXPECTED_LE 0xd5000000
>> #define FLAG(s) s->branch_stack->entries[i].flags
>>
>> --
>> 2.25.1
next prev parent reply other threads:[~2021-11-17 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 15:52 [PATCH] perf/test: Test case 27 broken on s390 in linux-next Thomas Richter
2021-11-06 19:32 ` Arnaldo Carvalho de Melo
2021-11-17 8:30 ` Madhavan Srinivasan [this message]
2021-11-17 8:26 ` PING " Thomas Richter
2021-11-17 9:05 ` Madhavan Srinivasan
2021-11-17 14:21 ` 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=d8943b3f-b2d5-8b5c-cbf9-14360a6df2b4@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=acme@kernel.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sumanthk@linux.ibm.com \
--cc=svens@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).