From: jean.pihet@linaro.org (Jean Pihet)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM64: add perf support
Date: Mon, 16 Dec 2013 18:42:05 +0100 [thread overview]
Message-ID: <CAFrcx1mUiQwgw_SCYPQrU4Jz90Zmp5_uR8HSBceDbEKSCxO1OQ@mail.gmail.com> (raw)
In-Reply-To: <20131216173214.GK20193@mudshark.cambridge.arm.com>
Hi Will,
On 16 December 2013 18:32, Will Deacon <will.deacon@arm.com> wrote:
> Jean,
>
> On Mon, Dec 16, 2013 at 04:54:30PM +0000, Jean Pihet wrote:
>> Add perf support for the AARCH64 architecture. This includes the
>> support for:
>
> To be fair, we do have perf support already. This is extending what we have
> by adding additional arch-specific stuff.
Ok I can change the descriptions accordingly.
>> - AARCH64 perf registers definition and hooks,
>> - compat mode registers use, i.e. profiling a 32-bit binary on
>> a 64-bit system,
>> - unwinding using the dwarf information from the .debug_frame
>> section of the ELF binary; only in 64-bit mode,
>> - unwinding using the frame pointer information; in 64-bit and
>> compat modes.
>
> Why did you send out two copies of this series to different lists? Which one
> should I be looking at?
The two copies actually are the same patches. I just forgot the l-a-k
ML address first and so re-sent the series. Sorry about that ;-|
> /confused
Thx for looking at the series!
>
> Will
Jean
prev parent reply other threads:[~2013-12-16 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 16:54 [PATCH 0/3] ARM64: add perf support Jean Pihet
2013-12-16 16:54 ` [PATCH 1/3] ARM64: perf: add support for perf registers API Jean Pihet
2013-12-16 16:54 ` [PATCH 2/3] ARM64: perf: wire up perf_regs and unwind support Jean Pihet
2013-12-16 16:54 ` [PATCH 3/3] ARM64: perf: add support for frame pointer unwinding in compat mode Jean Pihet
2013-12-16 17:32 ` [PATCH 0/3] ARM64: add perf support Will Deacon
2013-12-16 17:42 ` Jean Pihet [this message]
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=CAFrcx1mUiQwgw_SCYPQrU4Jz90Zmp5_uR8HSBceDbEKSCxO1OQ@mail.gmail.com \
--to=jean.pihet@linaro.org \
--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).