From: Alexis Berlemont <alexis.berlemont@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Alexis Berlemont <alexis.berlemont@gmail.com>,
peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
alexander.shishkin@linux.intel.com
Subject: [PATCH 0/3] perf: callchain-specific annotation
Date: Tue, 18 Apr 2017 00:55:17 +0200 [thread overview]
Message-ID: <20170417225520.28082-1-alexis.berlemont@gmail.com> (raw)
Hi,
These patches are a proposal to fulfill the following point of perf's TODO list
(https://perf.wiki.kernel.org/index.php/Todo):
* What I want is that if I am on bar*(), it annotates bar*(), no samples just
the call site (obtained from the callchain) dissassembly. This is useful
because in many cases there maybe multiple call sites within a function and
there maybe inlines in between. Hard to track down if you cannot figure out
the surrounding addresses of the call site. (Request made by Stephane
Eranian).
These patches are still at an early stage:
* Per-callchain annotation is only available in perf-report;
* Tests were not performed on real-world applications but on small basic ones.
Alexis.
Alexis Berlemont (3):
perf annotate: implement per-callchain annotation histogram
perf hists browser: add callchain-specific annotation
perf report: fill per-callchain symbol annotation histograms
tools/perf/builtin-report.c | 8 ++
tools/perf/ui/browsers/hists.c | 188 ++++++++++++++++++++++++-
tools/perf/util/annotate.c | 308 ++++++++++++++++++++++++++++++++++++++++-
tools/perf/util/annotate.h | 19 +++
4 files changed, 517 insertions(+), 6 deletions(-)
--
2.12.2
next reply other threads:[~2017-04-17 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 22:55 Alexis Berlemont [this message]
2017-04-17 22:55 ` [PATCH 1/3] perf annotate: implement per-callchain annotation histogram Alexis Berlemont
2017-04-17 22:55 ` [PATCH 2/3] perf hists browser: add callchain-specific annotation Alexis Berlemont
2017-04-17 22:55 ` [PATCH 3/3] perf report: fill per-callchain symbol annotation histograms Alexis Berlemont
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=20170417225520.28082-1-alexis.berlemont@gmail.com \
--to=alexis.berlemont@gmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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).