[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1234364503-857-3-git-send-email-matsu@igel.co.jp>
Date: Thu, 12 Feb 2009 00:01:41 +0900
From: Katsuya Matsubara <matsu@...l.co.jp>
To: linux-rt-users <linux-rt-users@...r.kernel.org>
Cc: Steven Rostedt <srostedt@...hat.com>, Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
Paul Mundt <lethal@...ux-sh.org>,
LKML <linux-kernel@...r.kernel.org>,
Katsuya Matsubara <matsu@...l.co.jp>
Subject: [PATCH RT 2/4] sh: enable interrupts in signal handling
Fully-preemptible kernel does not need interrupts disabled in signal
handling. The same treatment can be found in x86 and arm code.
Signed-off-by: Katsuya Matsubara <matsu@...l.co.jp>
---
arch/sh/kernel/signal_32.c | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/arch/sh/kernel/signal_32.c b/arch/sh/kernel/signal_32.c
index 6d6e408..9f633b5 100644
--- a/arch/sh/kernel/signal_32.c
+++ b/arch/sh/kernel/signal_32.c
@@ -571,6 +571,13 @@ static void do_signal(struct pt_regs *regs, unsigned int save_r0)
struct k_sigaction ka;
sigset_t *oldset;
+#ifdef CONFIG_PREEMPT_RT
+ /*
+ * Fully-preemptible kernel does not need interrupts disabled:
+ */
+ local_irq_enable();
+ preempt_check_resched();
+#endif
/*
* We want the common case to go fast, which
* is why we may in certain cases get here from
--
1.6.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists