From: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
To: Kajol Jain <kjain@linux.ibm.com>, acme@kernel.org
Cc: jolsa@redhat.com, namhyung@kernel.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
irogers@google.com, tmricht@linux.ibm.com,
rbernon@codeweavers.com, maddy@linux.ibm.com,
atrajeev@linux.vnet.ibm.com,
Ravi Bangoria <ravi.bangoria@linux.ibm.com>
Subject: Re: [PATCH] perf test: Skip test 68 for Powerpc
Date: Tue, 24 Nov 2020 15:04:53 +0530 [thread overview]
Message-ID: <4a2908ca-6b75-c688-ec3b-7f37783f08cc@linux.ibm.com> (raw)
In-Reply-To: <20201119135022.36340-1-kjain@linux.ibm.com>
On 11/19/20 7:20 PM, Kajol Jain wrote:
> Commit ed21d6d7c48e6e ("perf tests: Add test for PE binary format support")
> adds a WINDOWS EXE file named tests/pe-file.exe, which is
> examined by the test case 'PE file support'. As powerpc doesn't support
> it, we are skipping this test.
>
> Result in power9 platform before this patach:
> [command]# ./perf test -F 68
> 68: PE file support : Failed!
>
> Result in power9 platform after this patch:
> [command]# ./perf test -F 68
> 68: PE file support : Skip
>
> Signed-off-by: Kajol Jain <kjain@linux.ibm.com>
Reviewed-by: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
next prev parent reply other threads:[~2020-11-24 9:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 8:29 [PATCH] perf test: Omit test 68 for s390 Thomas Richter
2020-11-19 13:50 ` [PATCH] perf test: Skip test 68 for Powerpc Kajol Jain
2020-11-24 9:34 ` Ravi Bangoria [this message]
2020-12-07 16:35 ` Arnaldo Carvalho de Melo
2020-12-08 14:43 ` Thomas Richter
2020-12-08 17:02 ` Ravi Bangoria
2020-12-09 17:49 ` Arnaldo Carvalho de Melo
2020-12-10 5:52 ` Ravi Bangoria
2020-12-09 17:37 ` Arnaldo Carvalho de Melo
2020-11-19 13:55 ` [PATCH] perf test: Omit test 68 for s390 kajoljain
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=4a2908ca-6b75-c688-ec3b-7f37783f08cc@linux.ibm.com \
--to=ravi.bangoria@linux.ibm.com \
--cc=acme@kernel.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=kjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=namhyung@kernel.org \
--cc=rbernon@codeweavers.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).