Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756688AbYFXOHF (ORCPT ); Tue, 24 Jun 2008 10:07:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753279AbYFXOGy (ORCPT ); Tue, 24 Jun 2008 10:06:54 -0400 Received: from cantor2.suse.de ([195.135.220.15]:38913 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753980AbYFXOGw (ORCPT ); Tue, 24 Jun 2008 10:06:52 -0400 Date: Tue, 24 Jun 2008 16:07:29 +0200 From: Bernhard Walle To: "Yinghai Lu" Cc: x86@kernel.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, vgoyal@redhat.com Subject: Re: [PATCH 3/3] Limit E820 map when a user-defined memory map is specified Message-ID: <20080624160729.2bead69c@halley.suse.de> In-Reply-To: <86802c440806221311q5a65cdb6me24b45de5657359c@mail.gmail.com> References: <1213977420-1555-1-git-send-email-bwalle@suse.de> <1213977420-1555-4-git-send-email-bwalle@suse.de> <86802c440806201334s30cbc685se44326812841fdd2@mail.gmail.com> <20080622215635.7a0ebaae@kopernikus.site> <86802c440806221311q5a65cdb6me24b45de5657359c@mail.gmail.com> Organization: SUSE Linux Products GmbH X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.9; x86_64-suse-linux-gnu) X-Face: ,G!z)dEOMkc[Cu+sF64,T9^5r3b>/}#HBRL%D^j@\SZbr'Itl7q@1<*dgB?A7(_leO1Tc4^ D*WfvfwKcz;,@E^y+pNP%86n8o<&g-vToCXW:r>Y$jxY,`KT?{H!07=2|Jdt?0ba^C-Tnx50vIV8It vi&Sicl:sj`k2`y)E;ECFi;i7W-?t3%\kD*));q)+%-pQd^.r'W}oBBx=+.~Gu}&F;lS7.a-m>Rv"w pe`D'OV^?HJd$-)7<2T[naDPl6+bAj'+UYd]u]B^'.LYK$2jS Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 967 Lines: 27 * Yinghai Lu [2008-06-22 13:11]: > > On Sun, Jun 22, 2008 at 12:56 PM, Bernhard Walle wrote: > > * "Yinghai Lu" [2008-06-20 13:34]: > >> > >> any problem that you encountered without this patch? > > > > Sorry, forgot to answer that question. > > > > Yes, if you use mem=3G and take a dump, kexec builds the ELF core > > headers for the full memory size, which means that the dump is as large > > as the physical memory of the machine is, which doesn't make sense. > > can we use e820_update_range instead? so e820_setup_gap still can get > correct value? Yes, good idea. Patch is in the queue ... Bernhard -- Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development -- 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/