From: Jeremy Fitzhardinge Subject: Re: [PATCH RFC] x86/acpi: don't ignore I/O APICs just because there's no local APIC Date: Thu, 18 Jun 2009 12:14:40 -0700 Message-ID: <4A3A9220.4070807@goop.org> References: <4A329CF8.4050502@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Len Brown Cc: Xen-devel , the arch/x86 maintainers , Linux Kernel Mailing List , Ingo Molnar , "Eric W. Biederman" , "H. Peter Anvin" , Thomas Gleixner List-Id: xen-devel@lists.xenproject.org On 06/18/09 09:08, Len Brown wrote: >> In principle, the local APIC and the I/O APIC are distinct (but related) >> components, which can be independently present. >> > > bzzzzt, but thanks for playing:-) > Perhaps I should have expressed that a bit more clearly: you could, if mad, build a machine with I/O APICs and some other mechanism for delivering the interrupts to CPUs. In practice, I doubt anyone ever has, or ever would. The only actual exception I know of is Xen's replacement of the physical local APIC with a paravirtualized interrupt interface. J