From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM64: perf: add support for the perf registers and dwarf unwinding
Date: Fri, 15 Nov 2013 16:42:13 +0000 [thread overview]
Message-ID: <20131115164213.GJ19468@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <CA+b37P0YCPm+4PWJobTOv02M0-mZyf4w02fDrBVYT0wfPL_hpA@mail.gmail.com>
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
next prev parent reply other threads:[~2013-11-15 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 14:54 [PATCH 0/2] ARM64: perf: add support for the perf registers and dwarf unwinding Jean Pihet
2013-10-18 14:54 ` [PATCH 1/2] ARM64: perf: add support for perf registers API Jean Pihet
2013-10-25 13:14 ` Will Deacon
2013-10-18 14:54 ` [PATCH 2/2] ARM64: perf: wire up perf_regs and unwind support Jean Pihet
2013-10-24 14:50 ` Jiri Olsa
2013-10-24 16:14 ` Jean Pihet
2013-11-14 11:04 ` [PATCH 0/2] ARM64: perf: add support for the perf registers and dwarf unwinding Sandeepa Prabhu
2013-11-14 11:15 ` Jean Pihet
2013-11-14 11:24 ` Sandeepa Prabhu
2013-11-15 16:42 ` Will Deacon [this message]
2013-11-18 5:58 ` Sandeepa Prabhu
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=20131115164213.GJ19468@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).