From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: "Tim Bird" <tim.bird@am.sony.com>, "Ingo Molnar" <mingo@elte.hu>,
"linux kernel" <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH 2/2] ftrace: add function-graph tracer support for ARM v2
Date: Wed, 20 May 2009 09:11:50 +0100 [thread overview]
Message-ID: <20090520081150.GA22558@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20090520023432.GJ6066@nowhere>
On Wed, May 20, 2009 at 04:34:35AM +0200, Frederic Weisbecker wrote:
> On Fri, May 15, 2009 at 10:06:36PM +0100, Russell King - ARM Linux wrote:
> > However, I'm not sure that this code is entirely right (and I'm not
> > sure what's going on with this patch - my editor is randomly changing
> > the placement of characters in it. Are you submitting patches using
> > UTF-8 characters in the code?)
> >
> > > >> @@ -139,8 +144,16 @@ ENTRY(mcount)
> > > >> adr r0, ftrace_stub
> > > >> cmp r0, r2
> > > >> bne trace
> >
> > If this is r0 != ftrace_stub, go to trace. So the next block will
> > only be executed if r0 /was/ ftrace_stub, in which case it can't be
> > ftrace_graph_return.
>
> Ah! This part concerns the function tracer.
> Let's see how it looks like in the original code: (added more comments
> inside)
You've completely missed the point I was trying to make. Please go back
and re-read my email and think about precisely what's happening in the
assembly path, particularly which branches will be taken and which code
paths will be taken with various values of r2.
prev parent reply other threads:[~2009-05-20 8:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 22:38 Tim Bird
2009-05-02 0:11 ` Frederic Weisbecker
2009-05-02 15:15 ` Uwe Kleine-König
2009-05-02 19:21 ` Steven Rostedt
2009-05-09 16:14 ` Frédéric Weisbecker
2009-05-15 21:06 ` Russell King - ARM Linux
2009-05-20 2:34 ` Frederic Weisbecker
2009-05-20 8:11 ` Russell King - ARM Linux [this message]
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=20090520081150.GA22558@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=fweisbec@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tim.bird@am.sony.com \
--cc=u.kleine-koenig@pengutronix.de \
/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®