[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: Yinghai Lu <yhlu.kernel@xxxxxxxxx>
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Sun, 07 Sep 2008 17:02:11 -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:02:33 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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

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

Follow-Ups:
- Re: [Xen-devel] [PATCH 7 of 7] x86: always explicitly map acpi memory
  - From: Yinghai Lu

References:
- [Xen-devel] [PATCH 0 of 7] x86: lay groundwork for Xen domain 0 support
  - From: Jeremy Fitzhardinge
- [Xen-devel] [PATCH 7 of 7] x86: always explicitly map acpi memory
  - From: Jeremy Fitzhardinge
- Re: [Xen-devel] [PATCH 7 of 7] x86: always explicitly map acpi memory
  - From: Yinghai Lu

Prev by Date: Re: [Xen-devel] xm dump-core options are useless
Next by Date: [Xen-devel] Re: [PATCH 6 of 7] x86: use early_ioremap in __acpi_map_table
Previous by thread: Re: [Xen-devel] [PATCH 7 of 7] x86: always explicitly map acpi memory
Next by thread: Re: [Xen-devel] [PATCH 7 of 7] x86: always explicitly map acpi memory
Index(es):
- Date
- Thread

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