From: Steven Rostedt <rostedt@goodmis.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Rabin Vincent <rabin@rab.in>
Subject: Re: [PATCH] ftrace: recordmcount: avoid STT_FUNC symbols as base on ARM
Date: Tue, 17 May 2011 20:27:15 -0400 [thread overview]
Message-ID: <1305678435.26849.0.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20110517225020.GD2266@n2100.arm.linux.org.uk>
On Tue, 2011-05-17 at 23:50 +0100, Russell King - ARM Linux wrote:
> On Tue, May 17, 2011 at 12:10:29PM -0400, Steven Rostedt wrote:
> > On Wed, 2011-05-11 at 22:53 +0530, Rabin Vincent wrote:
> > > While find_secsym_ndx often finds the unamed local STT_SECTION, if a
> > > section has only one function in it, the ARM toolchain generates the
> > > STT_FUNC symbol before the STT_SECTION, and recordmcount finds this
> > > instead.
> > >
> > > This is problematic on ARM because in ARM ELFs, "if a [STT_FUNC] symbol
> > > addresses a Thumb instruction, its value is the address of the
> > > instruction with bit zero set (in a relocatable object, the section
> > > offset with bit zero set)". This leads to incorrect mcount addresses
> > > being recorded.
> > >
> > > Fix this by not using STT_FUNC symbols as the base on ARM.
> >
> > Hi Russell,
> >
> > Can you give me an Acked-by on this patch?
>
> It would be better for someone who knows the ELF format for ARM and
> its weirdnesses to ack this patch. I'm afraid my ARM ELF format
> knowledge was been superseded when EABI came along and introduced
> all sorts of new stuff.
OK, in that case, I'll just apply the patch.
Thanks!
-- Steve
next prev parent reply other threads:[~2011-05-18 0:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 17:23 Rabin Vincent
2011-05-17 16:10 ` Steven Rostedt
2011-05-17 22:50 ` Russell King - ARM Linux
2011-05-18 0:27 ` Steven Rostedt [this message]
2011-05-27 12:46 ` [tip:perf/urgent] ftrace/recordmcount: Avoid " tip-bot for Rabin Vincent
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=1305678435.26849.0.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rabin@rab.in \
/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
all inboxes | Powered by JetHome®