From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Tim Bird <tim.bird@am.sony.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/2] ftrace - add ftrace function_graph support on ARM
Date: Sat, 6 Mar 2010 20:18:49 +0000 [thread overview]
Message-ID: <20100306201849.GD13262@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4B91A39F.8050502@am.sony.com>
On Fri, Mar 05, 2010 at 04:36:47PM -0800, Tim Bird wrote:
> IRQENTRY_TEXT was added to vmlinux.lds.S (to eliminate
> a compiler error on kernel/trace/trace_functions_graph.c),
> although no routines were marked as __irq_entry.
Well, ARM already places the assembly exception text in its own separate
section for other reasons. We can't place it in two sections.
What is __irq_entry used for? Just the low level assembly or C functions?
WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ftrace - add ftrace function_graph support on ARM
Date: Sat, 6 Mar 2010 20:18:49 +0000 [thread overview]
Message-ID: <20100306201849.GD13262@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4B91A39F.8050502@am.sony.com>
On Fri, Mar 05, 2010 at 04:36:47PM -0800, Tim Bird wrote:
> IRQENTRY_TEXT was added to vmlinux.lds.S (to eliminate
> a compiler error on kernel/trace/trace_functions_graph.c),
> although no routines were marked as __irq_entry.
Well, ARM already places the assembly exception text in its own separate
section for other reasons. We can't place it in two sections.
What is __irq_entry used for? Just the low level assembly or C functions?
next prev parent reply other threads:[~2010-03-06 20:18 UTC|newest]
Thread overview: 18+ 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 0:36 ` Tim Bird
2010-03-06 20:18 ` Russell King - ARM Linux [this message]
2010-03-06 20:18 ` Russell King - ARM Linux
2010-10-09 17:50 ` Rabin Vincent
2010-10-09 17:50 ` Rabin Vincent
2010-10-09 19:37 ` Russell King - ARM Linux
2010-10-09 19:37 ` Russell King - ARM Linux
2010-10-10 22:06 ` Rabin Vincent
2010-10-10 22:06 ` Rabin Vincent
2010-10-11 8:25 ` Russell King - ARM Linux
2010-10-11 8:25 ` Russell King - ARM Linux
2010-10-11 17:15 ` Rabin Vincent
2010-10-11 17:15 ` Rabin Vincent
-- strict thread matches above, loose matches on Subject: below --
2010-03-06 0:31 Tim Bird
2010-03-06 3:28 ` Frederic Weisbecker
2010-10-09 17:43 ` Rabin Vincent
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=20100306201849.GD13262@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tim.bird@am.sony.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.