[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131115164213.GJ19468@mudshark.cambridge.arm.com>
Date: Fri, 15 Nov 2013 16:42:13 +0000
From: Will Deacon <will.deacon@....com>
To: Sandeepa Prabhu <sandeepa.prabhu@...aro.org>
Cc: Jean Pihet <jean.pihet@...aro.org>, Jiri Olsa <jolsa@...hat.com>,
Arnaldo <acme@...stprotocols.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linaro-kernel@...ts.linaro.org" <linaro-kernel@...ts.linaro.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Patch Tracking <patches@...aro.org>,
Jean Pihet <jean.pihet@...oldbits.com>
Subject: Re: [PATCH 0/2] ARM64: perf: add support for the perf registers and
dwarf unwinding
On Thu, Nov 14, 2013 at 11:04:04AM +0000, Sandeepa Prabhu wrote:
> Hi Jean,
>
> I have applied this patchset on aarch64 upstream branch,cross-compiled
> for arm64 and try running some tests for hardware breakpoints.
>
> I cross-compiled perf using linaro toolchain
> "gcc-linaro-aarch64-linux-gnu-4.7-2013.04-20130415_linux" as
> $ cd tools/perf/
> $ make LDFLAGS=-static ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu-
>
> Copied the static binary to my initrd image and tried running tests to
> place hw_breakpoint on an kernel symbol as:
>
> # perf record -e "mem:0xffffffc00013f640:x"
Right, but that's not a valid invocation of perf. You have to give it
something to record. Something like:
# perf record -e mem:0xffffffc00013f640:x -a -- sleep 10
for example.
Will
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists