Re: [Xen-devel] [PATCH v8 19/27] ARM: vITS: handle MAPTI command

On 12/04/17 01:44, Andre Przywara wrote: +/* + * For a given virtual LPI read the enabled bit and priority from the virtual + * property table and update the virtual IRQ's state in the given pending_irq. + * Must be called with the respective VGIC VCPU lock held. + */ +static int update_lpi_pro

Re: [Xen-devel] [PATCH v8 19/27] ARM: vITS: handle MAPTI command

Hi Andre, On 12/04/17 01:44, Andre Przywara wrote: +/* + * For a given virtual LPI read the enabled bit and priority from the virtual + * property table and update the virtual IRQ's state in the given pending_irq. + * Must be called with the respective VGIC VCPU lock held. + */ +static int updat

Re: [Xen-devel] [PATCH v8 19/27] ARM: vITS: handle MAPTI command

Hi, On 12/04/17 17:18, Julien Grall wrote: > Hi Andre, > > On 12/04/17 01:44, Andre Przywara wrote: >> The MAPTI commands associates a DeviceID/EventID pair with a LPI/CPU >> pair and actually instantiates LPI interrupts. >> We connect the already allocated host LPI to this virtual LPI, so that >

Re: [Xen-devel] [PATCH v8 19/27] ARM: vITS: handle MAPTI command

Hi Andre, On 12/04/17 01:44, Andre Przywara wrote: The MAPTI commands associates a DeviceID/EventID pair with a LPI/CPU pair and actually instantiates LPI interrupts. We connect the already allocated host LPI to this virtual LPI, so that any triggering LPI on the host can be quickly forwarded to

[Xen-devel] [PATCH v8 19/27] ARM: vITS: handle MAPTI command

The MAPTI commands associates a DeviceID/EventID pair with a LPI/CPU pair and actually instantiates LPI interrupts. We connect the already allocated host LPI to this virtual LPI, so that any triggering LPI on the host can be quickly forwarded to a guest. Beside entering the VCPU and the virtual LPI