From: Tim Blechmann <tim@klingt.org>
To: rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
mingo@elte.hu, tglx@linutronix.de, Tim Blechmann <tim@klingt.org>
Subject: [PATCH] [RT] preempt_disable_rt for CONFIG_PREEMPT_RT
Date: Thu, 11 Dec 2008 20:05:48 +0100 [thread overview]
Message-ID: <1229022348-32311-1-git-send-email-tim@klingt.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0812081218471.26257@gandalf.stny.rr.com>
in some cases, spinlocks are used to avoid preemption. does not work
correctly, when CONFIG_PREEMPT_RT is enabled.
therefore two new macros are introduced:
preempt_disable_rt/preempt_disable_rt behave like their equivalents, if
CONFIG_PREEMPT_RT is enabled, and as noops otherwise.
Signed-off-by: Tim Blechmann <tim@klingt.org>
---
include/linux/preempt.h | 10 ++++++++++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/include/linux/preempt.h b/include/linux/preempt.h
index 72b1a10..2526170 100644
--- a/include/linux/preempt.h
+++ b/include/linux/preempt.h
@@ -93,6 +93,16 @@ do { \
#endif
+#ifdef CONFIG_PREEMPT_RT
+#define preempt_disable_rt preempt_disable
+#define preempt_enable_rt preempt_enable
+#else
+#define
+#define preempt_disable_rt do { } while (0)
+#define preempt_enable_rt do { } while (0)
+#endif
+
+
#ifdef CONFIG_PREEMPT_NOTIFIERS
struct preempt_notifier;
--
1.5.6.3
next prev parent reply other threads:[~2008-12-11 19:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 14:34 [PATCH] [RT] avoid preemption in memory controller code Tim Blechmann
2008-12-08 16:42 ` Steven Rostedt
2008-12-08 17:07 ` Tim Blechmann
2008-12-08 17:23 ` Steven Rostedt
2008-12-11 19:05 ` Tim Blechmann [this message]
2008-12-09 1:13 ` Li Zefan
2008-12-09 1:32 ` KAMEZAWA Hiroyuki
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=1229022348-32311-1-git-send-email-tim@klingt.org \
--to=tim@klingt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®