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: Thu, 18 Jun 2009 18:38:41 -0700 Message-ID: References: <4A329CF8.4050502@goop.org> <4A35ACB3.9040501@goop.org> <4A36B3EC.7010004@goop.org> <4A37F4AE.5050902@goop.org> <4A392896.9090408@goop.org> <4A3A96BC.1000302@goop.org> <4A3AACFD.5020805@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: <4A3AACFD.5020805@goop.org> (Jeremy Fitzhardinge's message of "Thu\, 18 Jun 2009 14\:09\:17 -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 , Keir Fraser , "H. Peter Anvin" , Thomas Gleixner List-Id: xen-devel@lists.xenproject.org Jeremy Fitzhardinge writes: > Ah, OK. The pirq is set up for a specific domain rather than being > global (otherwise it would need some kind of "which domain can access > which pirq" table). dom0 can either create a pirq for itself or someone > else, and the final user of the pirq binds it to a domain-local evtchn. > > I think. I really haven't looked into the pci-passthrough parts very > closely yet. I certainly could not find the code that would let you setup a pirq for another domain. In fact the pirq code aka alloc_vectors appears to hard code dom0 in Xen 3.4. pci-passthrough since it is domU, and since you describe it as well isolated and comparatively simple should be a shoe in. Further as you describe it pci-passthrough is a subset of what we have to do for dom0. So if we can I would like to see the pci passthrough code get merged first. Eric