LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jonas Rabenstein <jonas.rabenstein@studium.uni-erlangen.de>
To: linux-perf-users@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Milian Wolff <milian.wolff@kdab.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Andi Kleen <ak@linux.intel.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Stephane Eranian <eranian@google.com>,
Jonas Rabenstein <jonas.rabenstein@studium.uni-erlangen.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] perf evsel: add inline functions to sample callchain output
Date: Wed, 20 Feb 2019 01:11:16 +0100 [thread overview]
Message-ID: <20190220001116.3b3yyndjjmqs3hmm@studium.uni-erlangen.de> (raw)
In-Reply-To: <6aab7b5b0816426fed3cb2f2a2ba08e73e4c51e2.1550600520.git.jonas.rabenstein@studium.uni-erlangen.de>
On Tue, Feb 19, 2019 at 07:38:10PM +0100, Jonas Rabenstein wrote:
> Whenever a callchain shall be printed search for each address whether
> inline information is available and add those symbols to the output
> if symbol_conf.inline_name is enabled.
>
> Signed-off-by: Jonas Rabenstein <jonas.rabenstein@studium.uni-erlangen.de>
> ---
> tools/perf/util/evsel_fprintf.c | 46 +++++++++++++++++++++++++++++++++
> 1 file changed, 46 insertions(+)
>
> diff --git a/tools/perf/util/evsel_fprintf.c b/tools/perf/util/evsel_fprintf.c
> index c710f687ddf4..9f9ece453dc4 100644
> --- a/tools/perf/util/evsel_fprintf.c
> +++ b/tools/perf/util/evsel_fprintf.c
> @@ -168,6 +168,49 @@ static int __fprintf_callchain_link(u64 ip, struct map *map, struct symbol *symb
> return printed;
> }
>
> +static int __fprintf_callchain_inlines(struct callchain_cursor_node *node,
> + bool first, int left_alignment,
> + unsigned int print_opts, FILE *fp)
> +{
> + int printed = 0;
> + struct inline_node *inline_node;
> + struct inline_list *ilist;
> + u64 addr;
> +
> + if (!symbol_conf.inline_name)
> + return 0;
> +
> + if (!node->map || !node->map->dso)
> + return 0;
> +
> + addr = node->map->map_ip(node->map, node->ip);
I stumbled across a problem with the usage of map_ip here. Using the map_ip
on dynamic binaries does resolve the inline symbols but it fails with static
ones. Using node->ip directly works for static binaries but fails for
static ones...
Is there a way to decide whether node->map->dso is a static or dynamic
object file? Furthermore, is it even correct for a static dso to have
map->map_ip set to map__map_ip instead of identity__map_ip?
> +
> + inline_node = inlines__tree_find(&node->map->dso->inlined_nodes,
> + addr);
> + if (!inline_node) {
> + inline_node = dso__parse_addr_inlines(node->map->dso,
> + addr, node->sym);
> + if (!inline_node)
> + return 0;
> + inlines__tree_insert(&node->map->dso->inlined_nodes,
> + inline_node);
> + }
> +
> + list_for_each_entry(ilist, &inline_node->val, list) {
> + if (ilist->symbol == node->sym)
> + break;
> +
> + printed += __fprintf_callchain_link(node->ip, node->map,
> + ilist->symbol,
> + ilist->srcline,
> + first, left_alignment,
> + print_opts, fp);
> + first = (first && printed == 0);
> + }
> +
> + return printed;
> +}
> +
> int sample__fprintf_callchain(struct perf_sample *sample, int left_alignment,
> unsigned int print_opts, struct callchain_cursor *cursor,
> FILE *fp)
> @@ -183,6 +226,9 @@ int sample__fprintf_callchain(struct perf_sample *sample, int left_alignment,
> if (!node)
> break;
>
> + printed += __fprintf_callchain_inlines(node, (printed == 0),
> + left_alignment,
> + print_opts, fp);
>
> printed += __fprintf_callchain_link(node->ip, node->map,
> node->sym, NULL,
> --
> 2.19.2
>
next prev parent reply other threads:[~2019-02-20 0:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 18:38 [PATCH 0/2] perf evsel: add support for inlined function in callchains Jonas Rabenstein
2019-02-19 18:38 ` [PATCH 1/2] perf evsel: split sample__fprintf_callchain in output and iteration Jonas Rabenstein
2019-02-19 18:38 ` [PATCH 2/2] perf evsel: add inline functions to sample callchain output Jonas Rabenstein
2019-02-20 0:11 ` Jonas Rabenstein [this message]
2019-02-20 10:59 ` [PATCHv2 " Jonas Rabenstein
2019-02-19 19:38 ` [PATCH 0/2] perf evsel: add support for inlined function in callchains Arnaldo Carvalho de Melo
2019-02-20 14:34 ` Jiri Olsa
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=20190220001116.3b3yyndjjmqs3hmm@studium.uni-erlangen.de \
--to=jonas.rabenstein@studium.uni-erlangen.de \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=milian.wolff@kdab.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tmricht@linux.ibm.com \
--subject='Re: [PATCH 2/2] perf evsel: add inline functions to sample callchain output' \
/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
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).