Messages in this thread | | | From | (Eric W. Biederman) | Date | Fri, 12 Jun 2009 13:35:35 -0700 | Subject | Re: [PATCH RFC] x86/acpi: don't ignore I/O APICs just because there's no local APIC |
| |
Jeremy Fitzhardinge <jeremy@goop.org> writes:
> Parse the ACPI MADT for I/O APIC information, even if the cpu has no > (apparent) local APIC (ie, the CPU's APIC feature flag is clear). > > In principle, the local APIC and the I/O APIC are distinct (but related) > components, which can be independently present. > > In practice this can happen in a Xen system, where the hypervisor has > full control over the local APICs, and delivers interrupts initiated by > the I/O APICs via Xen's event channel mechanism.
Xen is giving us a semi bogus acpi table?
What is the paravirt configuration model with Xen? Is it documented somewhere?
Eric
| |