From: keith mannthey <kmannth@us.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: andrew <akpm@osdl.org>, discuss <discuss@x86-64.org>,
lhms-devel <lhms-devel@lists.sourceforge.net>,
Andi Kleen <ak@suse.de>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Lhms-devel] [PATCH 1/10] hot-add-mem x86_64: acpi motherboard fix
Date: Mon, 07 Aug 2006 19:15:07 -0700 [thread overview]
Message-ID: <1155003308.5790.44.camel@keithlap> (raw)
In-Reply-To: <20060808110855.b3a004a5.kamezawa.hiroyu@jp.fujitsu.com>
On Tue, 2006-08-08 at 11:08 +0900, KAMEZAWA Hiroyuki wrote:
> On Mon, 07 Aug 2006 17:56:56 -0700
> keith mannthey <kmannth@us.ibm.com> wrote:
>
> > I know of no x86_64 hardware the supports empty node hot-add memory. If
> > it exists I would recommend using SPARSEMEM based hot-add. On HW I am
> > aware of there is always some memory present in a node at boot.
> >
> >
> O.K one more.
>
> I know x86_64 has ZONE_DMA32. A system boot with only memory below 4G
> has no avilable memory in ZONE_NORMAL. If a new memory above 4G is added,
> ZONE_NORMAL comes as *new* zone.
> ZONE_NORMAL is empty at boot, so it's not in zonelist at boot.
>
> is this not problem ?
Perhaps in this situation you could run into trouble. I am not sure if
I can put my hardware into this config but I will try.
Thanks for taking a look at these patches and the reserve path.
Thanks,
Keith
prev parent reply other threads:[~2006-08-08 2:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 13:13 [PATCH 1/10] hot-add-mem x86_64: acpi motherboard fix Keith Mannthey
2006-08-04 13:13 ` [PATCH 2/10] hot-add-mem x86_64: fixup externs Keith Mannthey
2006-08-04 13:14 ` [PATCH 3/10] hot-add-mem x86_64: Kconfig changes Keith Mannthey
2006-08-04 13:14 ` [PATCH 4/10] hot-add-mem x86_64: Enable SPARSEMEM in srat.c Keith Mannthey
2006-08-04 15:17 ` [Lhms-devel] " Mika Penttilä
2006-08-04 19:36 ` keith mannthey
2006-08-04 17:42 ` Dave Hansen
2006-08-04 13:14 ` [PATCH 5/10] hot-add-mem x86_64: memory_add_physaddr_to_nid enable Keith Mannthey
2006-08-04 13:14 ` [PATCH 7/10] hot-add-mem x86_64: x86_64 kernel mapping fix Keith Mannthey
2006-08-04 13:14 ` [PATCH 8/10] hot-add-mem x86_64: use CONFIG_MEMORY_HOTPLUG_SPARSE Keith Mannthey
2006-08-04 13:14 ` [PATCH 9/10] hot-add-mem x86_64: use CONFIG_MEMORY_HOTPLUG_RESERVE Keith Mannthey
2006-08-07 17:41 ` keith mannthey
2006-08-04 13:14 ` [PATCH 10/10] hot-add-mem x86_64: valid add range check Keith Mannthey
2006-08-05 5:39 ` [PATCH 1/10] hot-add-mem x86_64: acpi motherboard fix KAMEZAWA Hiroyuki
2006-08-05 5:51 ` KAMEZAWA Hiroyuki
2006-08-07 18:39 ` keith mannthey
2006-08-08 0:31 ` [Lhms-devel] " KAMEZAWA Hiroyuki
2006-08-08 0:56 ` keith mannthey
2006-08-08 2:08 ` KAMEZAWA Hiroyuki
2006-08-08 2:15 ` 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=1155003308.5790.44.camel@keithlap \
--to=kmannth@us.ibm.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=discuss@x86-64.org \
--cc=kamezawa.hiroyu@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox