From: ebiederm@xmission.com (Eric W. Biederman) Subject: Re: [PATCH RFC] x86/acpi: don't ignore I/O APICs just because there's no local APIC Date: Fri, 12 Jun 2009 13:35:35 -0700 Message-ID: References: <4A329CF8.4050502@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: <4A329CF8.4050502@goop.org> (Jeremy Fitzhardinge's message of "Fri\, 12 Jun 2009 11\:22\:48 -0700") List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: Xen-devel , the arch/x86 maintainers , Linux Kernel Mailing List , Ingo Molnar , "H. Peter Anvin" , Thomas Gleixner List-Id: xen-devel@lists.xenproject.org Jeremy Fitzhardinge 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