public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@cloudius-systems.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
	Avi Kivity <avi@cloudius-systems.com>
Subject: Re: [PATCH] perf tools: demangle kernel and kernel module symbols too
Date: Mon, 27 Jan 2014 16:14:24 +0200	[thread overview]
Message-ID: <52E669C0.7040002@cloudius-systems.com> (raw)
In-Reply-To: <26f71bf5bf7ee1408e3f1a803556d5df18223ef1.1390420726.git.avi@cloudius-systems.com>

On 01/22/2014 09:58 PM, Avi Kivity wrote:
> Some kernels contain C++ code, and thus their symbols need to be demangled.
> This allows 'perf kvm top' to generate readable output.

Ping?

> Signed-off-by: Avi Kivity <avi@cloudius-systems.com>
> ---
>   tools/perf/util/symbol-elf.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/symbol-elf.c b/tools/perf/util/symbol-elf.c
> index 7594567..8f12f0f 100644
> --- a/tools/perf/util/symbol-elf.c
> +++ b/tools/perf/util/symbol-elf.c
> @@ -922,6 +922,7 @@ int dso__load_sym(struct dso *dso, struct map *map,
>   				  (u64)shdr.sh_offset);
>   			sym.st_value -= shdr.sh_addr - shdr.sh_offset;
>   		}
> +new_symbol:
>   		/*
>   		 * We need to figure out if the object was created from C++ sources
>   		 * DWARF DW_compile_unit has this, but we don't always have access
> @@ -933,7 +934,6 @@ int dso__load_sym(struct dso *dso, struct map *map,
>   			if (demangled != NULL)
>   				elf_name = demangled;
>   		}
> -new_symbol:
>   		f = symbol__new(sym.st_value, sym.st_size,
>   				GELF_ST_BIND(sym.st_info), elf_name);
>   		free(demangled);


  reply	other threads:[~2014-01-27 14:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22 19:58 [PATCH] perf tools: demangle kernel and kernel module symbols too Avi Kivity
2014-01-27 14:14 ` Avi Kivity [this message]
2014-01-27 14:48   ` Arnaldo Carvalho de Melo
2014-02-02  8:54 ` [tip:perf/urgent] perf tools: Demangle " tip-bot for Avi Kivity

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=52E669C0.7040002@cloudius-systems.com \
    --to=avi@cloudius-systems.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulus@samba.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