From: Milian Wolff <milian.wolff@kdab.com>
To: Nan Xiao <xiaonan830818@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Why the stack frame in perf.data isn't displayed in FlameGraph?
Date: Thu, 18 May 2017 21:01:29 +0200 [thread overview]
Message-ID: <2393730.W62ke2LKls@agathebauer> (raw)
In-Reply-To: <CA+MhoaOJkUe-EyP67F+YtNb04TjfteTSS=KHiN98ry4zK5WXWA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
On Donnerstag, 18. Mai 2017 15:24:04 CEST Nan Xiao wrote:
> Hi Milian,
>
> Firstly, thanks very much for your kind and detailed help!
>
> (1) I recompile the program use "g++ -g -O2 ...", and use "perf record
> --call-graph dwarf" to sample. The FlameGraph can display full stack
> frames and "inner" function appears in both FlameGraph and "perf
> record".
>
> (2) > Also, to see inline frames, try to build perf from git (acme's
> perf/core) and use `perf report --inline`.
>
> I find my perf version doesn't support "--inline" option, and I can't
> figure out what is the meaning of "build perf from git (acme's
> perf/core)". Could you elaborate it? I just install perf tools using
> "sudo pacman -S perf".
Essentially it boils down to do this:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux -b perf/
core
cd linux/tools/perf
make
./perf report --inline ...
Cheers
--
Milian Wolff | milian.wolff@kdab.com | Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5903 bytes --]
next prev parent reply other threads:[~2017-05-18 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 4:09 Why the stack frame in perf.data isn't displayed in FlameGraph? Nan Xiao
2017-05-18 7:32 ` Milian Wolff
2017-05-18 13:24 ` Nan Xiao
2017-05-18 19:01 ` Milian Wolff [this message]
2017-05-19 1:50 ` Nan Xiao
2017-05-23 9:32 ` Milian Wolff
2017-05-23 10:14 ` Nan Xiao
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=2393730.W62ke2LKls@agathebauer \
--to=milian.wolff@kdab.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=xiaonan830818@gmail.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 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.