Re: x86_64: 2.6.14 with NUMA panics at boot

[Andi Kleen <ak@suse.de>]

On Monday 31 October 2005 02:40, Bob Picco wrote:
> Added Matt to cc:
> Andi Kleen wrote:	[Sun Oct 30 2005, 09:12:17PM EST]
>
> > On Monday 31 October 2005 01:17, Bob Picco wrote:
> > > This is a slightly modified patch I used on x86_64 for EXTREME testing.
> > > The original 2.6.13-rc1-mhp1 patch didn't apply cleanly against 2.6.14.
> > > It will apply with this untested patch.  The patch needs to have
> > > arch_sparse_init which is only active for SPARSEMEM. This patch was
> > > just for testing EXTREME on x86_64 NUMA and needs review.
> > >
> > > I think the bootmem allocator is being used before initialized.  This
> > > wouldn't have happened before SPARSEMEM_EXTREME became the default.
> > >
> > > If you feel my analysis is correct, I'll generate a cleaner patch and
> > > test on my 4 way.
> >
> > Ok the question is - why did nobody submit this patch in time? When
> > sparse was merged I assumed folks would actually test and maintain
> > it. But that doesn't seem to be the case? Somewhat surprising.
>
> Well I did post it on lhms mailing list. 

Fixes for code that is in mainline needs to go to the appropiate mainline 
mailing list (for x86-64 that is l-k and discuss@x86-64.org) and maintainers.

> However it's incomplete because 
> it doesn't address !NUMA. 

So i should not apply it yet?

-Andi