From: Tim Bird <tim.bird@am.sony.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>,
"linux kernel" <linux-kernel@vger.kernel.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Abhishek Sagar" <sagar.abhishek@gmail.com>,
"Russell King" <rmk@arm.linux.org.uk>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: Anyone working on ftrace function graph support on ARM?
Date: Tue, 24 Mar 2009 14:40:04 -0700 [thread overview]
Message-ID: <49C95334.5040106@am.sony.com> (raw)
In-Reply-To: <20090324213618.GC5975@nowhere>
Frederic Weisbecker wrote:
> Yes, ie:
>
> _Before jumping to the function entry hook, you must save
> the arguments for the traced function on the stack.
> On x86, its eax, edx and ecx.
> On arm, it will be r0-r3.
> Then you have to transmit the address of the traced function
> (it's on r14) and it's parent (must rely on fp for that).
> Then you call the entry hook and restore the old scratch/arg
> registers.
>
>
> _ On return hook it's pretty the same, (saving the scratch
> registers, especially the return value which should be on r0
> and r1 if I'm not wrong).
> But you'll have to get the original return address from the
> return handler and then put it on pc.
>
> Well it's a very naive listing, there are sometimes some problems.
> For example on x86-64, I had to save even some non-scratch registers
> before calling the return hook, I still don't know why.
Thanks - this is very helpful. I'll send patches around when
I get something going. Hopefully in the next week or two.
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================
next prev parent reply other threads:[~2009-03-24 21:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 19:38 Anyone working on ftrace function graph support on ARM? Tim Bird
2009-03-24 20:25 ` Ingo Molnar
2009-03-24 20:48 ` Tim Bird
2009-03-24 20:38 ` Uwe Kleine-König
2009-03-24 21:36 ` Frederic Weisbecker
2009-03-24 21:40 ` Tim Bird [this message]
2009-03-24 21:48 ` Ingo Molnar
2009-03-24 21:57 ` Frederic Weisbecker
2009-03-24 22:14 ` Ingo Molnar
2009-03-24 22:54 ` Frederic Weisbecker
2009-03-25 8:36 ` Russell King - ARM Linux
2009-03-25 16:00 ` Steven Rostedt
2009-03-25 17:13 ` Frederic Weisbecker
2009-03-25 20:27 ` [PATCH][GIT PULL] x86, function-graph: only save return values on x86_64 Steven Rostedt
2009-03-25 20:45 ` Jaswinder Singh Rajput
2009-03-25 21:26 ` Steven Rostedt
2009-04-08 16:09 ` Ingo Molnar
2009-04-08 16:37 ` Steven Rostedt
2009-04-08 16:41 ` Ingo Molnar
2009-04-08 17:40 ` Frederic Weisbecker
2009-03-24 22:29 ` Anyone working on ftrace function graph support on ARM? Abhishek Sagar
2009-03-24 22:48 ` Frederic Weisbecker
2009-03-25 8:42 ` Russell King - ARM Linux
2009-03-25 8:54 ` Ingo Molnar
2009-03-25 9:57 ` Russell King - ARM Linux
2009-03-25 10:45 ` Uwe Kleine-König
2009-03-25 11:21 ` Russell King - ARM Linux
2009-03-25 12:09 ` Uwe Kleine-König
2009-03-25 16:41 ` Tim Bird
2009-03-25 11:41 ` Frederic Weisbecker
2009-03-25 16:34 ` Tim Bird
2009-03-25 17:05 ` Uwe Kleine-König
2009-03-25 17:17 ` Russell King - ARM Linux
2009-03-25 18:37 ` Tim Bird
2009-03-25 18:41 ` Steven Rostedt
2009-03-27 12:58 ` Catalin Marinas
2009-04-09 15:29 ` Daniel Jacobowitz
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=49C95334.5040106@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=fweisbec@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rmk@arm.linux.org.uk \
--cc=rostedt@goodmis.org \
--cc=sagar.abhishek@gmail.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