From: Michael Ellerman <mpe@ellerman.id.au>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Anton Blanchard <anton@ozlabs.org>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
He Kuang <hekuang@huawei.com>
Subject: Re: [PATCH 2/2] perf annotate: add powerpc support
Date: Tue, 14 Jun 2016 13:40:47 +1000 [thread overview]
Message-ID: <1465875647.31436.0.camel@ellerman.id.au> (raw)
In-Reply-To: <20160610143822.GT18654@naverao1-tp.localdomain>
On Fri, 2016-06-10 at 20:08 +0530, Naveen N. Rao wrote:
> On 2016/06/10 10:36AM, Arnaldo Carvalho de Melo wrote:
> > Em Fri, Jun 10, 2016 at 06:32:51PM +0530, Naveen N. Rao escreveu:
> > > Convert ins__find() to a __weak function for generic functionality,
> > > while adding a powerpc-specific variant. We look at the function name
> > > for branch instructions and classify the instructions to one among a
> > > branch, a function call (branch with LR update) or a function return
> > > (branch to LR).
> >
> > How would this allow one to get a perf.data collected on a powerpc
> > system, transfer it to a x86-64 (or aarch64, to mention another
> > workstation wannabe chip) system and then try annotating it?
> >
> > There was a previous discussion about this, and it involved having all
> > yout ppc tables available as well as other arches tables, and then
> > choosing which one to use based on:
> >
> > normalize_arch(thread->mg->machine->env->arch)
> >
> > just like was done for support cross unwinding, see recent patch kit by
> > He Kuang, CCed.
>
> Nice. This would be good to have. I will look at adding powerpc support
> for cross-architecture unwind.
>
> However, for cross-architecture annotation, I think there will be a lot
> more dependencies since perf currently uses objdump to obtain the
> disassembly. In addition, the actual binaries will also be needed.
It's possible to build a multi-arch objdump, I don't know if it's packaged on
all distros, or if perf wants to depend on it.
cheers
next prev parent reply other threads:[~2016-06-14 3:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 13:02 [PATCH 1/2] perf annotate: generalize handling of ret instructions Naveen N. Rao
2016-06-10 13:02 ` [PATCH 2/2] perf annotate: add powerpc support Naveen N. Rao
2016-06-10 13:36 ` Arnaldo Carvalho de Melo
2016-06-10 14:38 ` Naveen N. Rao
2016-06-10 16:01 ` Naveen N. Rao
2016-06-14 3:40 ` Michael Ellerman [this message]
2016-06-14 12:46 ` Arnaldo Carvalho de Melo
2016-06-10 13:30 ` [PATCH 1/2] perf annotate: generalize handling of ret instructions Arnaldo Carvalho de Melo
2016-06-10 14:06 ` Naveen N. Rao
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=1465875647.31436.0.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=acme@kernel.org \
--cc=ananth@in.ibm.com \
--cc=anton@ozlabs.org \
--cc=hekuang@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.vnet.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).