From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Victor Kamensky <victor.kamensky@linaro.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
David Ahern <dsahern@gmail.com>,
Will Deacon <will.deacon@arm.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Jiri Olsa <jolsa@redhat.com>,
Avi Kivity <avi@cloudius-systems.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Anton Blanchard <anton@samba.org>,
Dave Martin <Dave.Martin@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2 2/3] perf symbols: improve abi compliance in arm mapping symbols handling
Date: Thu, 22 Jan 2015 15:29:08 +0000 [thread overview]
Message-ID: <20150122152908.GA26493@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1421902378-3634-3-git-send-email-victor.kamensky@linaro.org>
On Wed, Jan 21, 2015 at 08:52:57PM -0800, Victor Kamensky wrote:
> Both Arm and Aarch64 ELF ABI allow mapping symbols be in from
> either "$d" or "$d.<any>". But current code that handles mapping
> symbols only deals with the first, dollar character and a single
> letter, case.
>
> The patch adds handling of the second case with period
> followed by any characters.
>
> Suggested-by: Russell King <linux@arm.linux.org.uk>
> Suggested-by: Will Deacon <will.deacon@arm.com>
> Signed-off-by: Victor Kamensky <victor.kamensky@linaro.org>
> Acked-by: Will Deacon <will.deacon@arm.com>
> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Cc: Paul Mackerras <paulus@samba.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
> Cc: Adrian Hunter <adrian.hunter@intel.com>
> Cc: Jiri Olsa <jolsa@redhat.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Avi Kivity <avi@cloudius-systems.com>
> Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
> Cc: Anton Blanchard <anton@samba.org>
> Cc: David Ahern <dsahern@gmail.com>
> Cc: Dave Martin <Dave.Martin@arm.com>
> ---
> tools/perf/util/symbol-elf.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/tools/perf/util/symbol-elf.c b/tools/perf/util/symbol-elf.c
> index 1e188dd..7fd35d6 100644
> --- a/tools/perf/util/symbol-elf.c
> +++ b/tools/perf/util/symbol-elf.c
> @@ -857,17 +857,16 @@ int dso__load_sym(struct dso *dso, struct map *map,
> * don't identify functions, so will confuse the profile
> * output: */
> if (ehdr.e_machine == EM_ARM) {
> - if (!strcmp(elf_name, "$a") ||
> - !strcmp(elf_name, "$d") ||
> - !strcmp(elf_name, "$t"))
> + if (elf_name[0] == '$' && strchr("adt", elf_name[1])
> + && (elf_name[2] == '\0' || elf_name[2] == '.'))
> continue;
> }
> /* Reject Aarch64 ELF "mapping symbols": these aren't unique and
> * don't identify functions, so will confuse the profile
> * output: */
> if (ehdr.e_machine == EM_AARCH64) {
> - if (!strcmp(elf_name, "$x") ||
> - !strcmp(elf_name, "$d"))
> + if (elf_name[0] == '$' && strchr("dx", elf_name[1])
> + && (elf_name[2] == '\0' || elf_name[2] == '.'))
> continue;
> }
Why not fix this first? Then, all you'd need to do would be to change
the test for EM_ARM to EM_ARM or EM_AARCH64, and add the 'x' into the
strchr() string.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-01-22 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 4:52 [PATCH V2 0/3] perf symbols: debuglink and arm mapping symbols changes Victor Kamensky
2015-01-22 4:52 ` [PATCH V2 1/3] perf symbols: Ignore mapping symbols on aarch64 Victor Kamensky
2015-01-22 15:27 ` Russell King - ARM Linux
2015-01-22 4:52 ` [PATCH V2 2/3] perf symbols: improve abi compliance in arm mapping symbols handling Victor Kamensky
2015-01-22 15:29 ` Russell King - ARM Linux [this message]
2015-01-22 16:02 ` Victor Kamensky
2015-01-22 4:52 ` [PATCH V2 3/3] perf symbols: debuglink should take symfs option into account Victor Kamensky
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=20150122152908.GA26493@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=Dave.Martin@arm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=anton@samba.org \
--cc=avi@cloudius-systems.com \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=victor.kamensky@linaro.org \
--cc=will.deacon@arm.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 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).