[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1329254900.3772.10.camel@pasglop>
Date: Wed, 15 Feb 2012 08:28:20 +1100
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Arjan van de Ven <arjan@...radead.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, mikey@...ling.org,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
gregkh@...uxfoundation.org, Ingo Molnar <mingo@...e.hu>,
linux-kernel@...r.kernel.org, Milton Miller <miltonm@....com>,
Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"H. Peter Anvin" <hpa@...or.com>, arjanvandeven@...il.com,
Thomas Gleixner <tglx@...utronix.de>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
ppc-dev <linuxppc-dev@...ts.ozlabs.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
Subject: Re: smp: Start up non-boot CPUs asynchronously
On Tue, 2012-02-14 at 15:18 +0530, Srivatsa S. Bhat wrote:
> > 2. Just below that we have smp_cpus_done(setup_max_cpus); and this translates
> > to native_smp_cpus_done() under x86, which calls impress_friends().
> > And that means, the bogosum calculation and the total activated processor
> > count which is printed, may get messed up.
We also have code on powerpc that relies on the bringup having been
completed in smp_cpus_done(), especially on platforms that don't support
CPU hotplug (or fake it using sleep loops).
In some case we unmap MMIO space or close access to components (i2c for
example) that we use during the bringup for things like hard synchro of
CPU timebases, etc... on some G5s we disable the elastic interface on
the northbridge for CPUs that weren't brought up, that sort of thing...
So this patch will break a LOT of stuff for us, it must at least be a
config option for now, until we find another way to fix these things.
Cheers,
Ben.
--
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