From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) by kanga.kvack.org (Postfix) with ESMTP id 7623E6B0031 for ; Tue, 14 Jan 2014 10:23:44 -0500 (EST) Received: by mail-ie0-f176.google.com with SMTP id lx4so524613iec.35 for ; Tue, 14 Jan 2014 07:23:44 -0800 (PST) Received: from g1t0027.austin.hp.com (g1t0027.austin.hp.com. [15.216.28.34]) by mx.google.com with ESMTPS id qb5si2033442igc.7.2014.01.14.07.23.42 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 14 Jan 2014 07:23:43 -0800 (PST) Message-ID: <1389712628.1792.277.camel@misato.fc.hp.com> Subject: Re: [PATCH] x86, acpi memory hotplug, add parameter to disable memory hotplug From: Toshi Kani Date: Tue, 14 Jan 2014 08:17:08 -0700 In-Reply-To: <52D4A469.9090100@jp.fujitsu.com> References: <1389650161-13292-1-git-send-email-prarit@redhat.com> <52D47999.5080905@redhat.com> <52D48EC4.5070400@jp.fujitsu.com> <1389663689.1792.268.camel@misato.fc.hp.com> <52D4A469.9090100@jp.fujitsu.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Yasuaki Ishimatsu Cc: Prarit Bhargava , KOSAKI Motohiro , LKML , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , the arch/x86 maintainers , Len Brown , "Rafael J. Wysocki" , Linn Crosetto , Pekka Enberg , Yinghai Lu , Andrew Morton , Tang Chen , Wen Congyang , Vivek Goyal , Dave Young , linux-acpi@vger.kernel.org, "linux-mm@kvack.org" On Tue, 2014-01-14 at 11:43 +0900, Yasuaki Ishimatsu wrote: > (2014/01/14 10:41), Toshi Kani wrote: > > On Tue, 2014-01-14 at 10:11 +0900, Yasuaki Ishimatsu wrote: > > : > >>>> I think we need a knob manually enable mem-hotplug when specify memmap. But > >>>> it is another story. > >>>> > >>>> Acked-by: KOSAKI Motohiro > >>> > >>> As mentioned, self-NAK. I have seen a system that I needed to specify > >>> memmap=exactmap & had hotplug memory. I will only keep the acpi_no_memhotplug > >>> option in the next version of the patch. > >> > >> > >> Your following first patch is simply and makes sense. > >> > >> http://marc.info/?l=linux-acpi&m=138922019607796&w=2 > >> > > > > In this option, it also requires changing kexec-tools to specify the new > > option for kdump. It won't be simpler. > > Hmm. > I use memm= boot option and hotplug memory for memory hot-remove. > At least, the patch cannot be accepted. Do you mean mem=nG option? I am curious to know how memory hot-remove works in this case. Don't acpi_memhotplug add all the memory ranges at boot, and defeat the mem=nG option? Thanks, -Toshi -- 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