From: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>, Jiri Olsa <jolsa@redhat.com>
Cc: alexander.shishkin@linux.intel.com, namhyung@kernel.org,
tmricht@linux.ibm.com, sandipan@linux.ibm.com,
brueckner@linux.ibm.com, kim.phillips@arm.com,
kstewart@linuxfoundation.org, tglx@linutronix.de,
naveen.n.rao@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
Ravi Bangoria <ravi.bangoria@linux.ibm.com>
Subject: Re: [PATCH] perf test: Add watchpoint test
Date: Wed, 12 Sep 2018 08:38:45 +0530 [thread overview]
Message-ID: <f5bd0ead-166a-74e8-09fa-3c76d55e2503@linux.ibm.com> (raw)
In-Reply-To: <20180910173122.GC15516@kernel.org>
On 09/10/2018 11:01 PM, Arnaldo Carvalho de Melo wrote:
> Em Mon, Sep 10, 2018 at 11:18:30AM -0300, Arnaldo Carvalho de Melo escreveu:
>> Em Mon, Sep 10, 2018 at 10:47:54AM -0300, Arnaldo Carvalho de Melo escreveu:
>>> Em Mon, Sep 10, 2018 at 12:31:54PM +0200, Jiri Olsa escreveu:
>>>> On Mon, Sep 10, 2018 at 03:28:11PM +0530, Ravi Bangoria wrote:
>>>>> Ex on powerpc:
>>>>> $ sudo ./perf test 22
>>>>> 22: Watchpoint :
>>>>> 22.1: Read Only Watchpoint : Ok
>>>>> 22.2: Write Only Watchpoint : Ok
>>>>> 22.3: Read / Write Watchpoint : Ok
>>>>> 22.4: Modify Watchpoint : Ok
>
>>>> cool, thanks!
>
>>>> Acked-by: Jiri Olsa <jolsa@kernel.org>
>
>>> Thanks, applied.
>
> Oops, fails when cross-building it to mips, I'll try to fix after lunch:
Sorry for bit late reply. Will send v2 with the fix.
Thanks
Ravi
>
> 18 109.48 debian:experimental : Ok gcc (Debian 8.2.0-4) 8.2.0
> 19 42.66 debian:experimental-x-arm64 : Ok aarch64-linux-gnu-gcc (Debian 8.1.0-12) 8.1.0
> 20 22.33 debian:experimental-x-mips : FAIL mips-linux-gnu-gcc (Debian 8.1.0-12) 8.1.0
> 21 20.05 debian:experimental-x-mips64 : FAIL mips64-linux-gnuabi64-gcc (Debian 8.1.0-12) 8.1.0
> 22 22.85 debian:experimental-x-mipsel : FAIL mipsel-linux-gnu-gcc (Debian 8.1.0-12) 8.1.0
>
> CC /tmp/build/perf/tests/bp_account.o
> CC /tmp/build/perf/tests/wp.o
> tests/wp.c:5:10: fatal error: arch-tests.h: No such file or directory
> #include "arch-tests.h"
> ^~~~~~~~~~~~~~
> compilation terminated.
> mv: cannot stat '/tmp/build/perf/tests/.wp.o.tmp': No such file or directory
> make[4]: *** [/git/linux/tools/build/Makefile.build:97: /tmp/build/perf/tests/wp.o] Error 1
> make[4]: *** Waiting for unfinished jobs....
> CC /tmp/build/perf/util/record.o
> CC /tmp/build/perf/util/srcline.o
> make[3]: *** [/git/linux/tools/build/Makefile.build:139: tests] Error 2
> make[2]: *** [Makefile.perf:507: /tmp/build/perf/perf-in.o] Error 2
> make[2]: *** Waiting for unfinished jobs....
>
next prev parent reply other threads:[~2018-09-12 3:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 9:58 [PATCH] perf test: Add watchpoint test Ravi Bangoria
2018-09-10 10:31 ` Jiri Olsa
2018-09-10 13:47 ` Arnaldo Carvalho de Melo
2018-09-10 14:18 ` Arnaldo Carvalho de Melo
2018-09-10 17:31 ` Arnaldo Carvalho de Melo
2018-09-12 3:08 ` Ravi Bangoria [this message]
2018-09-12 3:15 ` Ravi Bangoria
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=f5bd0ead-166a-74e8-09fa-3c76d55e2503@linux.ibm.com \
--to=ravi.bangoria@linux.ibm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=brueckner@linux.ibm.com \
--cc=jolsa@redhat.com \
--cc=kim.phillips@arm.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=sandipan@linux.ibm.com \
--cc=tglx@linutronix.de \
--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).