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

RE: [Xen-devel] [PATCH] pci-ioapic-0502.patch


I tried the patch out on my dual proc x86_64 box running 32-bit SLES9. I
was able to boot the system successfully and bring up a VM. The only
thing which caught my eye was the following in the Dom0 boot. 

IOAPIC[0]: Invalid reference to IRQ 0

I am not even sure if this is an error. I have attached the complete
boot sequence.

I noticed that the I/O APICs are still being initialized by Xen. Are you
planning on moving this also to Dom0?


-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Arun Sharma
Sent: Monday, May 02, 2005 6:36 PM
To: Ian Pratt; Keir Fraser
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH] pci-ioapic-0502.patch

Move PCI device scanning to dom0. Enable ACPI in dom0. This should
reduce the complexity of xen and move the complexity of dealing with
hardware bugs and workarounds etc to dom0.

The ioapic local apic (and hence all the vectors) are owned by the
Dom0 enables the ACPI interpreter, handles PCI and ACPI based interrupt 

New hypercalls to assign vectors and for accessing the ioapic.

Functionality not yet provided:

o acpi=off to support machines with broken or no acpi support.
o support for driver domains 

Signed-off-by: Arun Sharma <arun.sharma@xxxxxxxxx>
Signed-off-by: Asit Mallick <asit.k.mallick@xxxxxxxxx>

Attachment: xen-3-devel-boot-intel.txt
Description: xen-3-devel-boot-intel.txt

Xen-devel mailing list



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