From: Jiri Olsa <jolsa@redhat.com>
To: "Vuille, Martin (Martin)" <vmartin@avaya.com>
Cc: Kim Phillips <kim.phillips@arm.com>,
Milian Wolff <milian.wolff@kdab.com>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>
Subject: Re: Records call-graphs on ARM, reporting on x86_64
Date: Mon, 12 Feb 2018 09:28:35 +0100 [thread overview]
Message-ID: <20180212082835.GA6253@krava> (raw)
In-Reply-To: <30C2D590D16A5C46ADFE6521910377989262DACC@AZ-US1EXMB02.global.avaya.com>
On Fri, Feb 09, 2018 at 11:26:26PM +0000, Vuille, Martin (Martin) wrote:
> > I thought files like arch/arm/include/perf_regs.h handled that; is that not the
> > case?
>
> That is true. But if perf is compiled for x86_64, then it is compiled with
> arch/x86/... and knows nothing of arch/arm/... The architecture selection is
> done at compile time.
right, seems like a problem for libdw, but it shouldn't be problem for
linwunwind where it's compiled in via util/libunwind/arm64.o
>
> > Some distros like Ubuntu provide cross unwind packages such as android-
> > libunwind[-dev], and I've been known to build unwind and dwarf libraries
> > from scratch to get the best results; not sure if this will help you though (I
> > work best given a list of commands that do or don't work).
> >
>
> elfutils/libdw supports all architectures by selecting at run-time based on
> the ELF header 'machine' type. So that's not an issue.
>
> I recompiled perf with 'ARCH=arm' on my x86_64 host and, with a few hacks
> and the fix to problem (2), it now works fine and can unwind my ARM call
> stacks just fine.
could you please share those hacks?
thanks,
jirka
next prev parent reply other threads:[~2018-02-12 8:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 16:13 Records call-graphs on ARM, reporting on x86_64 Vuille, Martin (Martin)
2018-02-08 16:30 ` Milian Wolff
2018-02-08 17:09 ` Vuille, Martin (Martin)
2018-02-09 18:06 ` Vuille, Martin (Martin)
2018-02-09 20:56 ` Kim Phillips
2018-02-09 23:26 ` Vuille, Martin (Martin)
2018-02-12 8:28 ` Jiri Olsa [this message]
2018-02-12 16:37 ` Vuille, Martin (Martin)
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=20180212082835.GA6253@krava \
--to=jolsa@redhat.com \
--cc=kim.phillips@arm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=milian.wolff@kdab.com \
--cc=vmartin@avaya.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