linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Milian Wolff <milian.wolff@kdab.com>, Linux-kernel@vger.kernel.org
Cc: linux-perf-users@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	David Ahern <dsahern@gmail.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] perf report: distinguish between inliners in the same function
Date: Tue, 2 May 2017 10:11:14 +0800	[thread overview]
Message-ID: <ec980cd2-f595-3ed5-5276-4d687480e621@linux.intel.com> (raw)
In-Reply-To: <20170427215950.6649-1-milian.wolff@kdab.com>


SNIP

> ~~~~~
> $ perf report --stdio --inline --no-children
> Failed to open [ext4], continuing without symbols
> # To display the perf.data header info, please use --header/--header-only
> options.
> #
> #
> # Total Lost Samples: 0
> #
> # Samples: 499  of event 'cycles'
> # Event count (approx.): 329354953
> #
> # Overhead  Command    Shared Object      Symbol
> # ........  .........  .................  ................................
> #
>      96.70%  ex_random  ex_random          [.] main
> |
>              ---main
>                 __libc_start_main
>                 _start
> ...
> ~~~~~
>
> Note how no inlined frames are actually shown, because the first
> sample in main points to an IP that does not correspond to any
> inlined frames.

perf report -g address --inline --stdio

Did you try with "-g address" option? It's sorted by address.

But anyway, I like this patch. It works well in my test.

Thanks
Jin Yao

  reply	other threads:[~2017-05-02  2:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-27 21:59 [PATCH] perf report: distinguish between inliners in the same function Milian Wolff
2017-05-02  2:11 ` Jin, Yao [this message]
2017-05-02  9:19   ` Milian Wolff

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=ec980cd2-f595-3ed5-5276-4d687480e621@linux.intel.com \
    --to=yao.jin@linux.intel.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=dsahern@gmail.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=milian.wolff@kdab.com \
    --cc=namhyung@kernel.org \
    /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).