public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org, y-goto@jp.fujitsu.com
Subject: Re: sparc64 bootup regression...
Date: Wed, 7 May 2008 15:25:28 -0700	[thread overview]
Message-ID: <20080507152528.8fa6a951.akpm@linux-foundation.org> (raw)
In-Reply-To: <200805080009.46012.rjw@sisk.pl>

On Thu, 8 May 2008 00:09:45 +0200
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> On Wednesday, 30 of April 2008, Andrew Morton wrote:
> > On Tue, 29 Apr 2008 23:12:41 -0700 (PDT) David Miller <davem@davemloft.net> wrote:
> > 
> > > 
> > > This commit causes bootup failures on sparc64:
> > > 
> > > commit 86f6dae1377523689bd8468fed2f2dd180fc0560
> > > Author: Yasunori Goto <y-goto@jp.fujitsu.com>
> > > 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@linux-foundation.org>
Date:   Wed Apr 30 00:55:17 2008 -0700

    revert "memory hotplug: allocate usemap on the section with pgdat"


  reply	other threads:[~2008-05-07 22:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30  6:12 sparc64 bootup regression David Miller
2008-04-30  6:38 ` Andrew Morton
2008-04-30  6:46   ` KAMEZAWA Hiroyuki
2008-04-30  7:15   ` KAMEZAWA Hiroyuki
2008-04-30  7:25     ` David Miller
2008-04-30  7:33       ` KAMEZAWA Hiroyuki
2008-04-30 12:53         ` Yasunori Goto
2008-06-03 22:14           ` David Miller
2008-06-04  5:05             ` Yasunori Goto
2008-04-30  7:30     ` Heiko Carstens
2008-04-30  7:44       ` KAMEZAWA Hiroyuki
2008-04-30  7:45         ` Heiko Carstens
2008-04-30  7:19   ` David Miller
2008-05-07 22:09   ` Rafael J. Wysocki
2008-05-07 22:25     ` Andrew Morton [this message]
2008-05-07 22:32       ` Rafael J. Wysocki
2008-05-07 22:46     ` David Miller
2008-05-01  5:13 ` powerpc boot regression Tony Breeds
2008-05-01 14:51   ` Badari Pulavarty
2008-05-01 19:01     ` Geoff Levand
2008-05-01 23:07     ` Tony Breeds
2008-05-03 12:05     ` Yasunori Goto

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=20080507152528.8fa6a951.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=y-goto@jp.fujitsu.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