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 22:45:55 +0530 [thread overview]
Message-ID: <AANLkTi=33EUPFLzTr3zRHL1+CEm7JpqU18cFzzmpbAsG@mail.gmail.com> (raw)
In-Reply-To: <20101011082535.GA26355@n2100.arm.linux.org.uk>
On Mon, Oct 11, 2010 at 1:55 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> And now to go back to the original question I asked: What is __irq_entry
> used for?
It's used to identify when we're inside the interrupt handling path.
Depending upon the tracing options ("funcgraph-irqs"), this can be
excluded from the trace output.
> If it's to identify those functions which can't be traced through because
> of the stack layout, that's true of all __exception marked functions -
> so we might as well make the linker symbols for irqentry alias the
> exception text symbols.
>
> I see nothing special of just the three functions you mention that warrant
> them being handled separately by ftrace.
See above. The funcgraph-irqs option is supposed to only affect the
interrupt handling path, not all exception handling.
next prev parent reply other threads:[~2010-10-11 17:15 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
2010-10-11 8:25 ` Russell King - ARM Linux
2010-10-11 17:15 ` Rabin Vincent [this message]
[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='AANLkTi=33EUPFLzTr3zRHL1+CEm7JpqU18cFzzmpbAsG@mail.gmail.com' \
--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).