RE: [Xen-devel] Re: [PATCH RFC] x86/acpi: don't ignore I/O APICs just because there's no local APIC

["Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>]

xen-devel-bounces@xxxxxxxxxxxxxxxxxxx wrote:
> I/O APICs just because there's no local APIC
> 
> Jeremy Fitzhardinge <jeremy@xxxxxxxx> 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 currently the GSI pirq is global, while MSI irq is per-domain. In fact, 
the irq for gsi is allocated by dom0 itself, and is shared by xen/dom0. I 
suspect this is partly because In 2.6.18 kernel, the irq/gsi is really messed 
up (I remember there is cleanup happen in 2.6.19).  

The domU get the pirq value through pci-backend and pci frontend driver. The 
user space tools will grant one pirq to a guest through hypercall and the 
permission information is saved in domain's structure.

When we switch to Jeremy's new method, maybe we can make the irq to be alocated 
by Xen HV, but I suspect it is ok to be kept still as global.

The MSI is using per-domain pirq.

--jyh

>> 
>> 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
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel