From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Russell King <linux@arm.linux.org.uk>
Subject: [patch 02/11] arm/irqs: Do not trace arch_local_{*,irq_*} functions
Date: Fri, 01 Jul 2011 23:04:37 -0400 [thread overview]
Message-ID: <20110702033853.026763006@goodmis.org> (raw)
In-Reply-To: 20110702030435.308336775@goodmis.org
[-- Attachment #1: 0002-arm-irqs-Do-not-trace-arch_local_-irq_-functions.patch --]
[-- Type: text/plain, Size: 3174 bytes --]
From: Steven Rostedt <srostedt@redhat.com>
Do not trace arch_local_save_flags(), arch_local_irq_*() and friends.
Although they are marked inline, gcc may still make a function out of
them and add it to the pool of functions that are traced by the function
tracer. This can cause undesirable results (kernel panic, triple faults,
etc).
Add the notrace notation to prevent them from ever being traced.
Cc: Russell King <linux@arm.linux.org.uk>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
arch/arm/include/asm/irqflags.h | 18 +++++++++---------
1 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/arch/arm/include/asm/irqflags.h b/arch/arm/include/asm/irqflags.h
index 1e6cca5..b633507 100644
--- a/arch/arm/include/asm/irqflags.h
+++ b/arch/arm/include/asm/irqflags.h
@@ -10,7 +10,7 @@
*/
#if __LINUX_ARM_ARCH__ >= 6
-static inline unsigned long arch_local_irq_save(void)
+static inline notrace unsigned long arch_local_irq_save(void)
{
unsigned long flags;
@@ -21,7 +21,7 @@ static inline unsigned long arch_local_irq_save(void)
return flags;
}
-static inline void arch_local_irq_enable(void)
+static inline notrace void arch_local_irq_enable(void)
{
asm volatile(
" cpsie i @ arch_local_irq_enable"
@@ -30,7 +30,7 @@ static inline void arch_local_irq_enable(void)
: "memory", "cc");
}
-static inline void arch_local_irq_disable(void)
+static inline notrace void arch_local_irq_disable(void)
{
asm volatile(
" cpsid i @ arch_local_irq_disable"
@@ -46,7 +46,7 @@ static inline void arch_local_irq_disable(void)
/*
* Save the current interrupt enable state & disable IRQs
*/
-static inline unsigned long arch_local_irq_save(void)
+static inline notrace unsigned long arch_local_irq_save(void)
{
unsigned long flags, temp;
@@ -63,7 +63,7 @@ static inline unsigned long arch_local_irq_save(void)
/*
* Enable IRQs
*/
-static inline void arch_local_irq_enable(void)
+static inline notrace void arch_local_irq_enable(void)
{
unsigned long temp;
asm volatile(
@@ -78,7 +78,7 @@ static inline void arch_local_irq_enable(void)
/*
* Disable IRQs
*/
-static inline void arch_local_irq_disable(void)
+static inline notrace void arch_local_irq_disable(void)
{
unsigned long temp;
asm volatile(
@@ -125,7 +125,7 @@ static inline void arch_local_irq_disable(void)
/*
* Save the current interrupt enable state.
*/
-static inline unsigned long arch_local_save_flags(void)
+static inline notrace unsigned long arch_local_save_flags(void)
{
unsigned long flags;
asm volatile(
@@ -137,7 +137,7 @@ static inline unsigned long arch_local_save_flags(void)
/*
* restore saved IRQ & FIQ state
*/
-static inline void arch_local_irq_restore(unsigned long flags)
+static inline notrace void arch_local_irq_restore(unsigned long flags)
{
asm volatile(
" msr cpsr_c, %0 @ local_irq_restore"
@@ -146,7 +146,7 @@ static inline void arch_local_irq_restore(unsigned long flags)
: "memory", "cc");
}
-static inline int arch_irqs_disabled_flags(unsigned long flags)
+static inline notrace int arch_irqs_disabled_flags(unsigned long flags)
{
return flags & PSR_I_BIT;
}
--
1.7.5.4
next prev parent reply other threads:[~2011-07-02 3:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110702030435.308336775@goodmis.org>
2011-07-02 3:04 ` [patch 01/11] x86/irqs: Do not trace arch_local_{*,irq_*} functions Steven Rostedt
2011-07-07 0:51 ` Steven Rostedt
2011-07-07 21:43 ` [tip:perf/core] tracing, x86/irq: Do not trace arch_local_{*,irq_*}() functions tip-bot for Steven Rostedt
2011-07-02 3:04 ` Steven Rostedt [this message]
2011-07-02 3:04 ` [patch 03/11] blackfin/irqs: Do not trace arch_local_{*,irq_*} functions Steven Rostedt
2011-07-02 6:50 ` Mike Frysinger
2011-07-02 16:11 ` Steven Rostedt
2011-07-02 16:39 ` Mike Frysinger
2011-07-02 16:40 ` Mike Frysinger
2011-07-05 12:51 ` Steven Rostedt
2011-07-05 16:20 ` Mike Frysinger
2011-07-05 19:07 ` Mike Frysinger
2011-07-05 19:13 ` Steven Rostedt
2011-07-05 19:25 ` Mike Frysinger
2011-07-02 3:04 ` [patch 04/11] ia64/irqs: " Steven Rostedt
2011-07-02 3:04 ` [patch 05/11] microblaze/irqs: " Steven Rostedt
2011-07-05 10:43 ` Michal Simek
2011-07-05 12:49 ` Steven Rostedt
2011-07-02 3:04 ` [patch 06/11] mips/irqs: " Steven Rostedt
2011-07-02 3:04 ` [patch 07/11] parisc/irqs: " Steven Rostedt
2011-07-02 3:04 ` [patch 08/11] powerpc/irqs: " Steven Rostedt
2011-07-02 3:04 ` [patch 09/11] s390/irqs: " Steven Rostedt
2011-07-04 8:10 ` Martin Schwidefsky
2011-07-05 12:49 ` Steven Rostedt
2011-07-02 3:04 ` [patch 10/11] sh/unicore32/irqs: " Steven Rostedt
2011-07-04 1:56 ` Guan Xuetao
2011-07-05 12:50 ` Steven Rostedt
2011-07-11 3:34 ` Paul Mundt
2011-07-13 1:36 ` Steven Rostedt
2011-07-02 3:04 ` [patch 11/11] sparc/irqs: " Steven Rostedt
2011-07-02 4:11 ` David Miller
2011-07-05 12:49 ` Steven Rostedt
2011-07-06 6:43 ` David Miller
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=20110702033853.026763006@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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