Re: [Xen-devel] [PATCH] Make the hypercall PHYSDEVOP_alloc_irq_v

On 09/03/09 06:14, Zhang, Xiantao wrote:
> IMO, dom0 should only cares about pirq(==GSI) and doesn't need to know the 
> ifno about vector and specific apic&pin at all. Since Xen also knows GSI 
> info, so dom0 and Xen can build irq mapping(xen's irq and dom0's pirq) 
> through it.

Yes, but if dom0 rebinds the pirq<->gsi association, will Xen maintain
its internal structures correctly?

>   Maybe we can get rid of ioapic in dom0 eventually. 
>   

Yes, I think so (see other mail).

    J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread]	Current Thread	[Next in Thread>
Re: [Xen-devel] [PATCH] Make the hypercall PHYSDEVOP_alloc_irq_vector hypercall dummy., Jeremy Fitzhardinge RE: [Xen-devel] [PATCH] Make the hypercall PHYSDEVOP_alloc_irq_vector hypercall dummy., Zhang, Xiantao Re: [Xen-devel] [PATCH] Make the hypercall PHYSDEVOP_alloc_irq_vector hypercall dummy., Jeremy Fitzhardinge <=

Previous by Date:

Re: [Xen-devel] RE: [PATCH] Don't free irqaction for com irq when release irq., Jeremy Fitzhardinge

Next by Date:

[Xen-devel] xen devel archive search, Mukesh Rathor

Previous by Thread:

RE: [Xen-devel] [PATCH] Make the hypercall PHYSDEVOP_alloc_irq_vector hypercall dummy., Zhang, Xiantao

Next by Thread:

Re: [Xen-devel] [PATCH 0/3] xen: msi support for Xen dom0, Jeremy Fitzhardinge

Indexes:

[Date] [Thread] [Top] [All Lists]