From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [PATCH 2/2] x86, e820 disable ACPI Memory Hotplug if memory mapping is specified by user [v2] Date: Mon, 13 Jan 2014 16:53:49 -0800 Message-ID: <52D48A9D.7000003@zytor.com> References: <1389380698-19361-1-git-send-email-prarit@redhat.com> <1389380698-19361-4-git-send-email-prarit@redhat.com> <52D32962.5050908@redhat.com> <52D4793E.8070102@redhat.com> <1389659632.1792.247.camel@misato.fc.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1389659632.1792.247.camel@misato.fc.hp.com> Sender: owner-linux-mm@kvack.org To: Toshi Kani , Prarit Bhargava Cc: KOSAKI Motohiro , Bodo Eggert <7eggert@gmx.de>, LKML , Thomas Gleixner , Ingo Molnar , the arch/x86 maintainers , Len Brown , "Rafael J. Wysocki" , Linn Crosetto , Pekka Enberg , Yinghai Lu , Andrew Morton , Tang Chen , Wen Congyang , Vivek Goyal , dyoung@redhat.com, linux-acpi@vger.kernel.org, "linux-mm@kvack.org" List-Id: linux-acpi@vger.kernel.org On 01/13/2014 04:33 PM, Toshi Kani wrote: > > I do not think it makes sense. You needed memmap=exactmap as a > workaround because the kernel did not boot with the firmware's memory > info. So, it's broken, and you requested the kernel to ignore the > firmware info. > > Why do you think memory hotplug needs to be supported under such > condition, which has to use the broken firmware info? > Even more than memory hotplug: what do we do with NUMA? Since we have already told the kernel "the firmware is bogus" it would seem that any NUMA optimizations would be a bit ... cantankerous at best, no? -hpa -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org