From: rabin@rab.in (Rabin Vincent)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ftrace - add ftrace function_graph support on ARM
Date: Mon, 11 Oct 2010 03:36:03 +0530 [thread overview]
Message-ID: <20101010220603.GA2723@debian> (raw)
In-Reply-To: <20101009193757.GB28183@n2100.arm.linux.org.uk>
On Sat, Oct 09, 2010 at 08:37:57PM +0100, Russell King - ARM Linux wrote:
> On Sat, Oct 09, 2010 at 11:20:50PM +0530, Rabin Vincent wrote:
> > It's used just for the C entry functions for interrupts: asm_do_IRQ()
> > and the IPI and local timer functions.
> >
> > AFAICS __exception seems to be used only for is_exception_text(). If
> > that's the case, would it be OK to just place those functions in
> > __irq_entry if ftrace is built and have is_exception_text() check that
> > section too?
>
> No. is_exception_text() is used to detect those functions which have
> a specific stack layout - which is that there's a pt_regs struct on the
> stack. Grouping other functions into that violates the expectation.
I'm not sure I follow. These functions (asm_do_IRQ(), do_IPI(), and
do_local_timer()) will be the only ones in __irq_entry. iow, __irq_entry
will contain nothing else except these functions. So we woudn't be
grouping other functions; it's just that some of the __exception
functions would be moved to the new section so that __exception and
__irq_entry combined will contain the functions with the specific stack
layout (and only those functions).
next prev parent reply other threads:[~2010-10-10 22:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 0:36 [PATCH 2/2] ftrace - add ftrace function_graph support on ARM Tim Bird
2010-03-06 20:18 ` Russell King - ARM Linux
2010-10-09 17:50 ` Rabin Vincent
2010-10-09 19:37 ` Russell King - ARM Linux
2010-10-10 22:06 ` Rabin Vincent [this message]
2010-10-11 8:25 ` Russell King - ARM Linux
2010-10-11 17:15 ` Rabin Vincent
[not found] <4B91A25E.5030707@am.sony.com>
2010-10-09 17:43 ` 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=20101010220603.GA2723@debian \
--to=rabin@rab.in \
--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;
as well as URLs for NNTP newsgroup(s).