From: Suresh Siddha <suresh.b.siddha@intel.com>
To: mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com, trenn@suse.de,
prarit@redhat.com, tj@kernel.org, rusty@rustcorp.com.au,
a.p.zijlstra@chello.nl, akpm@linux-foundation.org,
torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, suresh.b.siddha@intel.com,
youquan.song@intel.com
Subject: [patch v2 0/4] MTRR rendezvous deadlock fix and cleanups using stop_machine()
Date: Thu, 23 Jun 2011 11:19:25 -0700 [thread overview]
Message-ID: <20110623181925.983511592@sbsiddha-MOBL3.sc.intel.com> (raw)
Here is the v2 of the MTRR stop machine patchset.
First patch is a simple fix targeting 3.0 and the stable kernels.
This fixes the boot deadlock reported in the
https://bugzilla.novell.com/show_bug.cgi?id=672008
Second patch reorganizes the stop_cpus() code.
Third patch introduces stop_machine_from_inactive_cpu() so that we can do
stop machine from the cpu hotplug path, where the calling cpu is not
yet active.
Fourth patch uses the stop_machine() and stop_machine_from_inactive_cpu()
to implement the x86 MTRR rendezvous sequence and thus remove the duplicate
implementation of stop machine using stop_one_cpu_nowait().
changes from v1:
* update comments and use cpu active instead of the cpu online checks.
thanks,
suresh
next reply other threads:[~2011-06-23 18:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 18:19 Suresh Siddha [this message]
2011-06-23 18:19 ` [patch v2 1/4] x86, mtrr: lock stop machine during MTRR rendezvous sequence Suresh Siddha
2011-06-27 22:46 ` [tip:x86/urgent] " tip-bot for Suresh Siddha
2011-06-23 18:19 ` [patch v2 2/4] stop_machine: reorganize stop_cpus() implementation Suresh Siddha
2011-06-27 23:16 ` [tip:x86/mtrr] " tip-bot for Tejun Heo
2011-06-23 18:19 ` [patch v2 3/4] stop_machine: implement stop_machine_from_inactive_cpu() Suresh Siddha
2011-06-27 23:16 ` [tip:x86/mtrr] " tip-bot for Tejun Heo
2011-06-23 18:19 ` [patch v2 4/4] x86, mtrr: use stop_machine APIs for doing MTRR rendezvous Suresh Siddha
2011-06-27 23:16 ` [tip:x86/mtrr] " tip-bot for Suresh Siddha
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=20110623181925.983511592@sbsiddha-MOBL3.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=prarit@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=trenn@suse.de \
--cc=youquan.song@intel.com \
/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®