[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 7 of 7] x86: always explicitly map acpi memory


  • To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
  • From: "Yinghai Lu" <yhlu.kernel@xxxxxxxxx>
  • Date: Sun, 7 Sep 2008 17:14:51 -0700
  • Cc: Ingo Molnar <mingo@xxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Andi Kleen <andi@xxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, "H. Peter Anvin" <hpa@xxxxxxxxx>
  • Delivery-date: Sun, 07 Sep 2008 17:15:12 -0700
  • 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=BDHJlDhgdQQEXs+5akgjAPfeBHGwK1RcvhlkRjvq0EcZXoxDE2RjrXEJBG8Jc/ETTi WqHsH1PTSlu7c/CaU2LkibilrCcbQ8IJuQhZ3xzEL+At/QxVXLxxLze3JooHD0sInBWj Y1J5313yFUlN2C2gEqKtVHfbolowh5RQ1lxDw=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Sun, Sep 7, 2008 at 5:02 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> 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?
>

Acked-by: Yinghai Lu <yhlu.kernel@xxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.