Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756635AbYFVULr (ORCPT ); Sun, 22 Jun 2008 16:11:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754331AbYFVULj (ORCPT ); Sun, 22 Jun 2008 16:11:39 -0400 Received: from rv-out-0506.google.com ([209.85.198.231]:63741 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753771AbYFVULj (ORCPT ); Sun, 22 Jun 2008 16:11:39 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=G+NHTuREa47CQApneo8f6BFdPBC/9vRkodHVYvf6XSRGp6GZ0bD3D00Fn1tphyFyC7 HBOa/0IXbnC2VWzFljkDDRDtmEmGrZ5PxyOReaXRLfTQoK9Q0hBenoD3LyGjYQ7ulBaT OLixl7noSM9DddN8DSKXg+BZSbvEiRe6FxxIY= Message-ID: <86802c440806221311q5a65cdb6me24b45de5657359c@mail.gmail.com> Date: Sun, 22 Jun 2008 13:11:38 -0700 From: "Yinghai Lu" To: "Bernhard Walle" Subject: Re: [PATCH 3/3] Limit E820 map when a user-defined memory map is specified Cc: x86@kernel.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, vgoyal@redhat.com In-Reply-To: <20080622215635.7a0ebaae@kopernikus.site> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 785 Lines: 20 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? YH -- 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/