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>,
Clark Williams <clark.williams@gmail.com>
Subject: [PATCH RT 0/3][FYI only] 3.2-rt cpu hotplug fix (hack)
Date: Mon, 05 Mar 2012 21:38:35 -0500 [thread overview]
Message-ID: <20120306023835.775610473@goodmis.org> (raw)
This is an FYI patch set only. It fixes a lot of the races that the
current -rt patch has with stressing hotplug.
Although this patch set (well patch one really) does prove to solve a
lot of the race conditions caused by notifiers waiting on tasks
that may be on the CPU going down, the patch itself is not at the
state that it should be accepted.
I'm posting this only for those that need a current fix while we work
on a real fix. Again, this patch set is an actual fix to several issues
with hotplug. But it makes the code even more hacky and there's
better ways to solve the issues.
I've been running my CPU hotplug stress test and a distcc kernel
compile (-j20) on a 4 way machine for the last 30 minutes (both in a
while loop) and it's still going strong.
This patch set goes on top of 3.2.9-rt15
Have fun,
-- Steve
next reply other threads:[~2012-03-06 2:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 2:38 Steven Rostedt [this message]
2012-03-06 2:38 ` [PATCH RT 1/3][FYI only] cpu/rt: Rework cpu down for PREEMPT_RT Steven Rostedt
2012-03-06 2:38 ` [PATCH RT 2/3][FYI only] workqueue: Revert workqueue: Fix PF_THREAD_BOUND abuse Steven Rostedt
2012-03-06 2:38 ` [PATCH RT 3/3][FYI only] workqueue: Revert workqueue: Fix cpuhotplug trainwreck 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=20120306023835.775610473@goodmis.org \
--to=rostedt@goodmis.org \
--cc=C.Emde@osadl.org \
--cc=clark.williams@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox