From: sshtylyov@mvista.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] fix perf Annotation of Thumb code
Date: Fri, 21 Jan 2011 20:17:18 +0300 [thread overview]
Message-ID: <4D39BF9E.3030007@ru.mvista.com> (raw)
In-Reply-To: <20110121163922.GA31398@davesworkthinkpad>
Hello.
Dr. David Alan Gilbert wrote:
> In ARM's Thumb mode the bottom bit of the symbol address is set to mark
> the function as Thumb; the instructions are in reality 2 or 4 byte on 2
> byte alignments, and when the +1 address is used in annotate it causes
> objdump to disassemble invalid instructions.
> The patch removes that bottom bit during symbol loading.
> This patch is against current linus's git, (2b1caf.....).
> Many thinks to Dave Martin for comments on an initial version of the patch.
> Dave
> (For reference this corresponds to this bug
> https://bugs.launchpad.net/linux-linaro/+bug/677547 )
> Signed-off-by: Dr. David Alan Gilbert <david.gilbert@linaro.org>
Hm, I think there should be no spaces/tabs before signoff...
> ---
> diff --git a/tools/perf/util/symbol.c b/tools/perf/util/symbol.c
> index 15ccfba..36e76c1 100644
> --- a/tools/perf/util/symbol.c
> +++ b/tools/perf/util/symbol.c
> @@ -1161,6 +1161,13 @@ static int dso__load_sym(struct dso *self, struct map *map, const char *name,
>
> section_name = elf_sec__name(&shdr, secstrs);
>
> + /* On ARM, symbols for thumb functions have 1 added to
> + * the symbol address as a flag - remove it */
> + if ((ehdr.e_machine == EM_ARM) &&
> + (map->type == MAP__FUNCTION) &&
> + (sym.st_value & 1))
> + sym.st_value-=1;
The coding style used suggests spaces around -=.
WBR, Sergei
next prev parent reply other threads:[~2011-01-21 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 16:40 [PATCH] fix perf Annotation of Thumb code Dr. David Alan Gilbert
2011-01-21 17:13 ` Arnaldo Carvalho de Melo
2011-01-21 17:17 ` Sergei Shtylyov [this message]
2011-01-21 17:40 ` Arnaldo Carvalho de Melo
2011-01-21 17:50 ` David Gilbert
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=4D39BF9E.3030007@ru.mvista.com \
--to=sshtylyov@mvista.com \
--cc=linux-arm-kernel@lists.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