Linux Perf Users
 help / color / mirror / Atom feed
From: Milian Wolff <milian.wolff@kdab.com>
To: "Vuille, Martin (Martin)" <vmartin@avaya.com>
Cc: "linux-perf-users@vger.kernel.org" <linux-perf-users@vger.kernel.org>
Subject: Re: Records call-graphs on ARM, reporting on x86_64
Date: Thu, 08 Feb 2018 17:30:55 +0100	[thread overview]
Message-ID: <2197547.58bztnllri@milian-kdab2> (raw)
In-Reply-To: <30C2D590D16A5C46ADFE6521910377989262C15B@AZ-US1EXMB02.global.avaya.com>

[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]

On Thursday, February 8, 2018 5:13:24 PM CET Vuille, Martin (Martin) wrote:
> I would like to collect call-graphs on my ARM target and examine them on my
> x86_64 host. I have no debug info on the ARM target; it is available on the
> x86_64 host.
> 
> On the ARM, I am passing the '--call-graph dwarf' option to 'perf record'.
> As I understand it, this collects user stacks for each event and the
> unwinding is done by 'perf report' using DWARF debug info.
> 
> When I look at the data with 'perf report', most of the call stacks contain
> "bogus" addresses that are in data (e.g., stack) or unmapped areas of the
> process address space. (This is pure C/C++ code, there's no JITing that I
> know of.)
> 
> What I am unclear about is whether DWARF is DWARF or whether there are "ARM
> DWARF" and "x86_64 DWARF". And if the latter is true, what do I need to do
> to interpret "ARM DWARF" on my x86_64 host?

Afaik this is not yet implemented in perf report when you use libunwind. When 
you use elfutils instead of unwinding, it could work if I'm not mistaken.

Independently from that, hotspot [1] should support the above usecase just 
fine.

[1]: https://github.com/KDAB/hotspot

Bye

-- 
Milian Wolff | milian.wolff@kdab.com | Senior Software Engineer
KDAB (Deutschland) GmbH, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt, C++ and OpenGL Experts

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3826 bytes --]

  reply	other threads:[~2018-02-08 16:31 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 [this message]
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
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=2197547.58bztnllri@milian-kdab2 \
    --to=milian.wolff@kdab.com \
    --cc=linux-perf-users@vger.kernel.org \
    --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