From: Jin Yao <yao.jin@linux.intel.com>
To: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com
Cc: Linux-kernel@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com,
Jin Yao <yao.jin@linux.intel.com>
Subject: [PATCH v2 0/2] perf report: Support annotation of code without symbols
Date: Fri, 21 Feb 2020 10:46:06 +0800 [thread overview]
Message-ID: <20200221024608.1847-1-yao.jin@linux.intel.com> (raw)
For perf report on stripped binaries it is currently impossible to do
annotation. The annotation state is all tied to symbols, but there are
either no symbols, or symbols are not covering all the code.
We should support the annotation functionality even without symbols.
The first patch uses al_addr to print because it's easy to dump
the instructions from this address in binary for branch mode.
The second patch supports the annotation on stripped binary.
v2:
---
Fix a crash issue when annotating an address in "unknown" object.
Jin Yao (2):
perf util: Print al_addr when symbol is not found
perf annotate: Support interactive annotation of code without symbols
tools/perf/ui/browsers/hists.c | 51 +++++++++++++++++++++++++++++-----
tools/perf/util/annotate.h | 2 ++
tools/perf/util/sort.c | 6 ++--
3 files changed, 50 insertions(+), 9 deletions(-)
--
2.17.1
next reply other threads:[~2020-02-21 2:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 2:46 Jin Yao [this message]
2020-02-21 2:46 ` [PATCH v2 1/2] perf util: Print al_addr when symbol is not found Jin Yao
2020-02-21 2:46 ` [PATCH v2 2/2] perf annotate: Support interactive annotation of code without symbols Jin Yao
2020-02-21 14:45 ` Jiri Olsa
2020-02-21 23:37 ` Jin, Yao
2020-02-23 19:50 ` Jiri Olsa
2020-02-24 0:28 ` Jin, Yao
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=20200221024608.1847-1-yao.jin@linux.intel.com \
--to=yao.jin@linux.intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.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.