From: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
To: acme@kernel.org, mpe@ellerman.id.au
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
anton@ozlabs.org, ananth@in.ibm.com, dja@axtens.net,
naveen.n.rao@linux.vnet.ibm.com, David.Laight@ACULAB.COM,
rmk+kernel@arm.linux.org.uk,
Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
Subject: Re: [PATCH v4 0/3] perf annotate: Enable cross arch annotate
Date: Wed, 13 Jul 2016 15:15:02 +0530 [thread overview]
Message-ID: <57860D9E.7000906@linux.vnet.ibm.com> (raw)
In-Reply-To: <1467952813-5797-1-git-send-email-ravi.bangoria@linux.vnet.ibm.com>
Arnaldo, Michael,
I've tested this patchset on ppc64 BE and LE both. Please review this.
-Ravi
On Friday 08 July 2016 10:10 AM, Ravi Bangoria wrote:
> Perf can currently only support code navigation (branches and calls) in
> annotate when run on the same architecture where perf.data was recorded.
> But cross arch annotate is not supported.
>
> This patchset enables cross arch annotate. Currently I've used x86
> and arm instructions which are already available and adding support
> for powerpc as well. Adding support for other arch will be easy.
>
> I've created this patch on top of acme/perf/core. And tested it with
> x86 and powerpc only.
>
> Note for arm:
> Few instructions were defined under #if __arm__ which I've used as a
> table for arm. But I'm not sure whether instruction defined outside of
> that also contains arm instructions. Apart from that, 'call__parse()'
> and 'move__parse()' contains #ifdef __arm__ directive. I've changed it
> to if (!strcmp(norm_arch, arm)). I don't have a arm machine to test
> these changes.
>
> Example:
>
> Record on powerpc:
> $ ./perf record -a
>
> Report -> Annotate on x86:
> $ ./perf report -i perf.data.powerpc --vmlinux vmlinux.powerpc
>
> Changes in v4:
> - powerpc: Added support for branch instructions that includes 'ctr'
> - __maybe_unused was misplaced at few location. Corrected it.
> - Moved position of v3 last patch that define macro for each arch name
>
> v3 link: https://lkml.org/lkml/2016/6/30/99
>
> Naveen N. Rao (1):
> perf annotate: add powerpc support
>
> Ravi Bangoria (2):
> perf: Define macro for normalized arch names
> perf annotate: Enable cross arch annotate
>
> tools/perf/arch/common.c | 36 ++---
> tools/perf/arch/common.h | 11 ++
> tools/perf/builtin-top.c | 2 +-
> tools/perf/ui/browsers/annotate.c | 3 +-
> tools/perf/ui/gtk/annotate.c | 2 +-
> tools/perf/util/annotate.c | 273 ++++++++++++++++++++++++++++++-------
> tools/perf/util/annotate.h | 6 +-
> tools/perf/util/unwind-libunwind.c | 4 +-
> 8 files changed, 265 insertions(+), 72 deletions(-)
>
> --
> 2.5.5
>
next prev parent reply other threads:[~2016-07-13 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 4:40 [PATCH v4 0/3] perf annotate: Enable cross arch annotate Ravi Bangoria
2016-07-08 4:40 ` [PATCH v4 1/3] perf: Define macro for normalized arch names Ravi Bangoria
2016-07-08 4:40 ` [PATCH v4 2/3] perf annotate: Enable cross arch annotate Ravi Bangoria
2016-07-08 4:40 ` [PATCH v4 3/3] perf annotate: add powerpc support Ravi Bangoria
2016-07-13 9:45 ` Ravi Bangoria [this message]
2016-08-19 5:41 ` [PATCH v4 0/3] perf annotate: Enable cross arch annotate 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=57860D9E.7000906@linux.vnet.ibm.com \
--to=ravi.bangoria@linux.vnet.ibm.com \
--cc=David.Laight@ACULAB.COM \
--cc=acme@kernel.org \
--cc=ananth@in.ibm.com \
--cc=anton@ozlabs.org \
--cc=dja@axtens.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=rmk+kernel@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.