[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v3 13/24] xen/arm: Implement hypercall PHYSDEVOP_{, un}map_pirq



>>> On 04.03.15 at 15:37, <julien.grall@xxxxxxxxxx> wrote:
> I looked to the interface of XENDOMCTL_bind_pt_irq and I'm not sure
> about the meaning of machine_irq and isa_irq.
> 
> AFAIU the code:
>       machine_irq => guest PIRQ

Yes (i.e. the Xen assigned representation of an IRQ the guest has
been granted access to).

>       isa_irq => host IRQ

But only for ISA ones, not PCI (i.e. you likely don't care about this
at all).

Note that the PCI case here still lacks a segment number - if you in
the end decided you want/need non-zero segments on ARM, then
this will need extension (which it would need anyway if anyone was
serious about to running Xen on such [x86] hardware).

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.