Re: sparc64 bootup regression...

[Rafael J. Wysocki]

On Thursday, 8 of May 2008, Andrew Morton wrote:
> On Thu, 8 May 2008 00:09:45 +0200
> "Rafael J. Wysocki" <rjw@xxxxxxx> wrote:
> 
> > On Wednesday, 30 of April 2008, Andrew Morton wrote:
> > > On Tue, 29 Apr 2008 23:12:41 -0700 (PDT) David Miller <davem@xxxxxxxxxxxxx> wrote:
> > > 
> > > > 
> > > > This commit causes bootup failures on sparc64:
> > > > 
> > > > commit 86f6dae1377523689bd8468fed2f2dd180fc0560
> > > > Author: Yasunori Goto <y-goto@xxxxxxxxxxxxxx>
> > > > Date:   Mon Apr 28 02:13:33 2008 -0700
> > > > 
> > > >     memory hotplug: allocate usemap on the section with pgdat
> > > >     
> > > >     Usemaps are allocated on the section which has pgdat by this.
> > > >     
> > > >     Because usemap size is very small, many other sections usemaps are allocated
> > > >     on only one page.  If a section has usemap, it can't be removed until removing
> > > >     other sections.  This dependency is not desirable for memory removing.
> > > >     
> > > >     Pgdat has similar feature.  When a section has pgdat area, it must be the last
> > > >     section for removing on the node.  So, if section A has pgdat and section B
> > > >     has usemap for section A, Both sections can't be removed due to dependency
> > > >     each other.
> > > >     
> > > >     To solve this issue, this patch collects usemap on same section with pgdat.
> > > >     If other sections doesn't have any dependency, this section will be able to be
> > > >     removed finally.
> > > 
> > > Thanks.  Does a straightforward revert fix it?  If so, we could do that while heads
> > > are being scratched.
> > 
> > Has that been reverted already?
> 
> yes, it has.
> 
> commit 5167464446e527b5a3b5618ba0baff93048bcbbe
> Author: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
> Date:   Wed Apr 30 00:55:17 2008 -0700
> 
>     revert "memory hotplug: allocate usemap on the section with pgdat"

OK, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/