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

RE: [Xen-devel] [PATCH][HVM] fix the ACPI dsdt inconsistency

  • To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, "He, Qing" <qing.he@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Yu, Ke" <ke.yu@xxxxxxxxx>
  • Date: Thu, 12 Oct 2006 21:31:30 +0800
  • Delivery-date: Thu, 12 Oct 2006 06:32:55 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acbt38QkYzxrw7CkQ2mEIUsdo2Cn/QAHZ5BhAABeU7gAADXhQA==
  • Thread-topic: [Xen-devel] [PATCH][HVM] fix the ACPI dsdt inconsistency

Keir Fraser wrote:
>> Looks like this just adds I/O memory and IRQ wire coverage 'big
>> enough' to happen to cover the requirements of the extra device?
>> That sounds okay to me, just want to confirm that's what's going on.

Yes, this is exactly what this patch does. This will provide enough MMIO and 
IRQ resource for xen_patform PCI device. Thus the resource conflict in windows 
will be resolved.

> Also, should we add something to the PRTA section, to give a default
> binding for Slot5/INTA?

PRTA happen to already have the extra entry: Package(){0x0004ffff, 0, 0, 11},  
// Device 4 , INTA
What PRTA missing is the entry for bus 0 device 0 (0x0000ffff). Fortunately, 
bus 0 device 0 is the host bridge, and no IRQ is needed for this device. So it 
doesn't matter. 

>  -- Keir

Xen-devel mailing list



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