Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753402AbaAJJgR (ORCPT ); Fri, 10 Jan 2014 04:36:17 -0500 Received: from fgwmail6.fujitsu.co.jp ([192.51.44.36]:39354 "EHLO fgwmail6.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751148AbaAJJgN (ORCPT ); Fri, 10 Jan 2014 04:36:13 -0500 X-SecurityPolicyCheck: OK by SHieldMailChecker v2.0.1 X-SHieldMailCheckerPolicyVersion: FJ-ISEC-20120718-3 Message-ID: <52CFBECB.9040309@jp.fujitsu.com> Date: Fri, 10 Jan 2014 18:35:07 +0900 From: Yasuaki Ishimatsu User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Baoquan CC: Toshi Kani , Vivek Goyal , , "Rafael J. Wysocki" , , , , , Subject: Re: kdump failed because of hotplug memory adding in kdump kernel References: <20140109145035.GB25897@redhat.com> <1389283439.1792.66.camel@misato.fc.hp.com> <20140109162427.GF25897@redhat.com> <1389288265.1792.108.camel@misato.fc.hp.com> <20140109182310.GG25897@redhat.com> <1389292470.1792.109.camel@misato.fc.hp.com> <20140109212705.GC12111@redhat.com> <1389304583.1792.139.camel@misato.fc.hp.com> <20140110071124.GA6464@dhcp-16-105.nay.redhat.com> <52CFAA20.2010109@jp.fujitsu.com> <20140110091433.GA14074@dhcp-16-105.nay.redhat.com> In-Reply-To: <20140110091433.GA14074@dhcp-16-105.nay.redhat.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-SecurityPolicyCheck-GC: OK by FENCE-Mail Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org (2014/01/10 18:14), Baoquan wrote: > > >In ns >>> object tree, they are not treated as hotplug memory. >> >> wrong. >> They are treated as hotplug memory. But the memory cannot hot removed >> because the memory has kernel memory. >> >>> Otherwise, any hotplug memory which is not reserved for 2nd kernel can >>> be parsed and need be added as hotplug memory, and add them into movable >>> zone. >> >> wrong. >> The memory is allocated as normal zone and it is offline. > > Hi, > > Thanks for answering. > > I am confused. Now the fact is in 1st kernel memory is reserved for > crashkernel and passed to 2nd kernel by exactmap. Then in 2nd kernel, > reserved memory regions are added into e820. Later hotplug memory still > trigger add_memory, and cause bug I reported. Does the issue occur even if you apply the following Prarit's patch to your kernel and add no_memory_hotplug boot option to 2nd kernel? http://marc.info/?l=linux-acpi&m=138922019607796&w=2 Thanks, Yasuaki Ishimatsu > > >> >>> >>> Am I right? >>> >> >>> The other question, e820 reserve is done earlier than acpi >>> initialization, because acpi_early_init() invocation is very late in >>> start_kernel(). Does that means at the very beginning all memorys are in >>> e820, later when acpi_early_init is called, hotplug memory is detected, >>> they will be moved to different place or need be marked with a specific >>> flag? >> >> No. >> >> Thanks, >> Yasuaki Ishimatsu >> > > -- > To unsubscribe from this list: send the line "unsubscribe linux-acpi" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/