From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx1.redhat.com ([209.132.183.28]) by merlin.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1WHxix-0000ps-Uv for kexec@lists.infradead.org; Mon, 24 Feb 2014 15:45:45 +0000 Date: Mon, 24 Feb 2014 10:45:19 -0500 From: Vivek Goyal Subject: Re: [PATCH v2 0/4] kexec-tools, x86: E820 memmap pass for kdump Message-ID: <20140224154518.GE4631@redhat.com> References: <1392888512-4473-1-git-send-email-chaowang@redhat.com> <20140224145841.GE1262@dhcp-17-89.nay.redhat.com> <20140224152205.GC4631@redhat.com> <1972414.2B2S29ZK0k@skinner> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1972414.2B2S29ZK0k@skinner> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=twosheds.infradead.org@lists.infradead.org To: Thomas Renninger Cc: jdmason@kudzu.us, kexec@lists.infradead.org, horms@verge.net.au, ebiederm@xmission.com, hpa@zytor.com, dyoung@redhat.com, WANG Chao On Mon, Feb 24, 2014 at 04:34:26PM +0100, Thomas Renninger wrote: [..] > > > How could this replace saved_max_pfn? The highest memory in kdump can't > > > necessarily be the real ram size. In kdump, RAM range is just part of the > > > real ram, not mentioning we don't pass RESERVED range to kdump E820. > I expected you pass RAM that must not be used as RESERVED. Then, still > depending on which mem type is the last one, it might have worked. No we don't. There is a proposal though to pass first kernel's reserved ranges to second kernel as SGI folks need that somehow. Thanks Vivek _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec