Re: [patch] Fix large MCA bootmem allocation

From: Russ Anderson <rja_at_sgi.com>
Date: 2008-02-07 10:32:02
On Wed, Feb 06, 2008 at 09:13:33AM -0600, Russ Anderson wrote:
> On Tue, Feb 05, 2008 at 04:00:09PM -0800, Luck, Tony wrote:
> > > Given that ia64_mca_cpu_init() does not get called in
> > > the hot-plug path
> > 
> > Surely it must be ...
> 
> That's what I thought, until testing showed otherwise.

My bad.  Additional testing shows ia64_mca_cpu_init() does get called.

I suspect my problem was when CONFIG_HOTPLUG_CPU was turned on,
not all the files were rebuilt.  
 
> The two code paths are setup_arch->cpu_init->ia64_mca_cpu_init
> for the boot processor and 
> start_secondary->cpu_init->ia64_mca_cpu_init for the other cpus
> at boot time.

In the hot-plug path, __cpu_up -> start_seconday .
 
> >                        you even have code in it to cope
> > with this case.  The:
> > 
> > 	if (__per_cpu_mca[cpu]) {
> > 
> > test can only be true if we are back in this code for a
> > second run through if the cpu was taken offline and added
> > again. Just like it says in the comment above this test.
> 
> Written on the assumption that the hot-plug code would
> eventually call it. 

It does.  The second time through the old memory is re-used.

Sorry about the noise...

-- 
Russ Anderson, OS RAS/Partitioning Project Lead  
SGI - Silicon Graphics Inc          rja@sgi.com
-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Received on Thu Feb 07 10:32:15 2008

This archive was generated by hypermail 2.1.8 : 2008-02-07 10:32:34 EST