From: Keir Fraser Subject: Re: Re: [PATCH RFC] x86/acpi: don't ignore I/O APICs just because there's no local APIC Date: Sat, 20 Jun 2009 11:22:38 +0100 Message-ID: References: <0A882F4D99BBF6449D58E61AAFD7EDD62F1B68F3@pdsmsx502.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <0A882F4D99BBF6449D58E61AAFD7EDD62F1B68F3@pdsmsx502.ccr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Tian, Kevin" , "Eric W. Biederman" Cc: Jeremy Fitzhardinge , Xen-devel , the arch/x86 maintainers , Linux Kernel Mailing List , Ingo Molnar , "Nakajima, Jun" , "H. Peter Anvin" , Thomas Gleixner , Len Brown List-Id: xen-devel@lists.xenproject.org On 20/06/2009 09:57, "Tian, Kevin" wrote: > So the real trouble is ACPI , which encode all platform bits if > they're not included in any existing BUS spec, such as power, > thermal, processor, battery, PCI routing, hotplug, EC, etc. Some > are owned by dom0 and some by Xen. However ACPI's AML encoding > makes automatic division between two categories really difficult. Yes, we share the same lament regarding ACPI. I'm not sure what the best (cleanest, simplest, whatever) solution really is going forward. We're certainly happy to make quite fundamental changes in Xen if there is sufficient win to be had. -- Keir