From: Jeremy Fitzhardinge Subject: Re: [PATCH 7 of 7] x86: always explicitly map acpi memory Date: Sun, 07 Sep 2008 17:02:11 -0700 Message-ID: <48C46B83.70704@goop.org> References: <6f23bad119ae2ed00f1c.1220826079@localhost> <86802c440809071635l1457659bufeefa6e65cc34bdf@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <86802c440809071635l1457659bufeefa6e65cc34bdf@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Yinghai Lu Cc: Ingo Molnar , Xen Devel , Andi Kleen , linux-kernel@vger.kernel.org, "H. Peter Anvin" List-Id: xen-devel@lists.xenproject.org Yinghai Lu wrote: > actually, > case 1: acpi tables near mmio, range, we don't map them from > 2.6.27-rc1, and it is bigger than max_low_mapped... > case 2: some strange system put acpi in the middle of RAM... like when > 8G ram installed, but MMIO is 3.5G, BIOS put acpi tables around 2G.. > OK, so what's your conclusion? Is this change OK or not? J