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

[Julien Grall <julien.grall@xxxxxxxxxx>]

Hi,

On 23/02/15 16:02, Ian Campbell wrote:
> On Mon, 2015-02-23 at 15:51 +0000, Julien Grall wrote:
>> On 20/02/15 16:53, Ian Campbell wrote:
> 
>>> Are we absolutely 100% sure that we will never ever want to map hardware
>>> IRQs to guests on ARMs using pirq-type event channels? Because that is
>>> what we are essentially ruling out here.
>>
>> That would happen if we decide to implement an interrupt controller
>> which doesn't support virtualization.
> 
> Good point. It's pretty unlikely but not absolutely impossible. So we
> should avoid reusing the pirq evtchn type for this. Jan suggested
> XENDOMCTL_bind_pt_irq which is looking better and better...

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
        isa_irq => host IRQ

am I right?

Regards,

-- 
Julien Grall

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