From: keith mannthey <kmannth@us.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: andrew <akpm@osdl.org>, lkml <linux-kernel@vger.kernel.org>,
Konrad redhat <konradr@redhat.com>,
dick zickus <dzickus@redhat.com>,
lhms-devel <lhms-devel@lists.sourceforge.net>
Subject: Re: [Patch] x86_64 hot-add memroy srat.c fix
Date: Mon, 16 Oct 2006 11:56:38 -0700 [thread overview]
Message-ID: <1161024998.5664.17.camel@keithlap> (raw)
In-Reply-To: <200610161201.16140.ak@suse.de>
On Mon, 2006-10-16 at 12:01 +0200, Andi Kleen wrote:
> On Saturday 07 October 2006 00:53, keith mannthey wrote:
> > This patch corrects the logic used in srat.c to figure out what
> > parsing what action to take when registering hot-add areas. Hot-add
> > areas should only be added to the node information for the
> > MEMORY_HOTPLGU_RESERVE case. When booting MEMORY_HOTPLUG_SPARSE hot-add
> > areas on everything but the last node are getting include in the node
> > data and during kernel boot the pages are setup then the kernel dies
> > when the pages are used. This patch fixes this issue. It is based
> > against 2.6.19-rc1.
>
> Added thanks, especially since it's a obvious typo.
Yea... Something pre 2.6.19 was removing the e820 reserved area before
the nodes were brought online (and thus masking the problem during
testing).
> If that patch was added to .19 does sparsemem hotadd work then or does it
> need more patches?
SPARSEMEM hot-add will work in .19 if this patch is applied.
Thanks,
Keith
prev parent reply other threads:[~2006-10-16 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 22:53 [Patch] x86_64 hot-add memroy srat.c fix keith mannthey
2006-10-16 10:01 ` Andi Kleen
2006-10-16 18:56 ` keith mannthey [this message]
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=1161024998.5664.17.camel@keithlap \
--to=kmannth@us.ibm.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=dzickus@redhat.com \
--cc=konradr@redhat.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.