[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1389663614.1792.267.camel@misato.fc.hp.com>
Date: Mon, 13 Jan 2014 18:40:14 -0700
From: Toshi Kani <toshi.kani@...com>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Prarit Bhargava <prarit@...hat.com>,
KOSAKI Motohiro <kosaki.motohiro@...il.com>,
Bodo Eggert <7eggert@....de>,
LKML <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
the arch/x86 maintainers <x86@...nel.org>,
Len Brown <lenb@...nel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Linn Crosetto <linn@...com>, Pekka Enberg <penberg@...nel.org>,
Yinghai Lu <yinghai@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Tang Chen <tangchen@...fujitsu.com>,
Wen Congyang <wency@...fujitsu.com>,
Vivek Goyal <vgoyal@...hat.com>, dyoung@...hat.com,
linux-acpi@...r.kernel.org,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [PATCH 2/2] x86, e820 disable ACPI Memory Hotplug if memory
mapping is specified by user [v2]
On Mon, 2014-01-13 at 17:29 -0800, H. Peter Anvin wrote:
> On 01/13/2014 05:09 PM, Toshi Kani wrote:
> >
> > In majority of the cases, memmap=exactmap is used for kdump and the
> > firmware info is sane. So, I think we should keep NUMA enabled since it
> > could be useful when multiple CPUs are enabled for kdump.
> >
>
> Rather unlikely since all of the kdump memory is likely to sit in a
> single node.
Right, but CPUs are distributed into multiple nodes, which dump the 1st
kernel's memory. So, these CPUs should dump their local memory ranges.
Thanks,
-Toshi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists