From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org,
linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>
Subject: [PATCH RT 2/5] cpu/rt: Fix cpu_hotplug variable initialization
Date: Tue, 17 Jul 2012 22:04:29 -0400 [thread overview]
Message-ID: <20120718020510.766031014@goodmis.org> (raw)
In-Reply-To: 20120718020427.338763317@goodmis.org
[-- Attachment #1: 0002-cpu-rt-Fix-cpu_hotplug-variable-initialization.patch --]
[-- Type: text/plain, Size: 842 bytes --]
From: Steven Rostedt <srostedt@redhat.com>
The commit "cpu/rt: Rework cpu down for PREEMPT_RT" changed the double
meaning of the cpu_hotplug.lock, where it was a spinlock for RT and a
mutex for non-RT, to just a mutex for both. But the initialization of
the variable was not updated to reflect this change.
Cc: stable-rt@vger.kernel.org
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
kernel/cpu.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/kernel/cpu.c b/kernel/cpu.c
index 0964e93..8f87b72 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -54,11 +54,7 @@ static struct {
int refcount;
} cpu_hotplug = {
.active_writer = NULL,
-#ifdef CONFIG_PREEMPT_RT_FULL
- .lock = __SPIN_LOCK_UNLOCKED(cpu_hotplug.lock),
-#else
.lock = __MUTEX_INITIALIZER(cpu_hotplug.lock),
-#endif
.refcount = 0,
};
--
1.7.10.4
next prev parent reply other threads:[~2012-07-18 2:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 2:04 [PATCH RT 0/5] [ANNOUNCE] 3.2.23-rt37-rc1 stable review Steven Rostedt
2012-07-18 2:04 ` [PATCH RT 1/5] cpu/rt: Rework cpu down for PREEMPT_RT Steven Rostedt
2012-07-18 2:04 ` Steven Rostedt [this message]
2012-07-18 2:04 ` [PATCH RT 3/5] workqueue: Revert workqueue: Fix PF_THREAD_BOUND abuse Steven Rostedt
2012-07-18 2:04 ` [PATCH RT 4/5] workqueue: Revert workqueue: Fix cpuhotplug trainwreck Steven Rostedt
2012-07-18 2:04 ` [PATCH RT 5/5] Linux 3.2.23-rt37-rc1 Steven Rostedt
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=20120718020510.766031014@goodmis.org \
--to=rostedt@goodmis.org \
--cc=C.Emde@osadl.org \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.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 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.