On 04/04/17 13:51, Andre Przywara wrote:
On 04/04/17 12:49, Julien Grall wrote:
On 03/04/17 15:18, Andre Przywara wrote:
Hi,
Hi Andre,
On 24/03/17 12:03, Julien Grall wrote:
+/* We may have mapped more host LPIs than the guest actually
asked for. */
Another way, is the interrupt ha
Hi,
On 04/04/17 12:49, Julien Grall wrote:
>
>
> On 03/04/17 15:18, Andre Przywara wrote:
>> Hi,
>
> Hi Andre,
>
>> On 24/03/17 12:03, Julien Grall wrote:
+/* We may have mapped more host LPIs than the guest actually
asked for. */
>>>
>>> Another way, is the interrupt has been re
On 03/04/17 15:18, Andre Przywara wrote:
Hi,
Hi Andre,
On 24/03/17 12:03, Julien Grall wrote:
+/* We may have mapped more host LPIs than the guest actually
asked for. */
Another way, is the interrupt has been received at the same time the
guest is configuring it. What will happen if
Hi,
On 24/03/17 12:03, Julien Grall wrote:
> Hi Andre,
>
> On 03/16/2017 11:20 AM, Andre Przywara wrote:
>> Upon receiving an LPI, we need to find the right VCPU and virtual IRQ
>> number to get this IRQ injected.
>> Iterate our two-level LPI table to find this information quickly when
>> the hos
Hi Andre,
On 03/16/2017 11:20 AM, Andre Przywara wrote:
Upon receiving an LPI, we need to find the right VCPU and virtual IRQ
number to get this IRQ injected.
Iterate our two-level LPI table to find this information quickly when
the host takes an LPI. Call the existing injection function to let
Upon receiving an LPI, we need to find the right VCPU and virtual IRQ
number to get this IRQ injected.
Iterate our two-level LPI table to find this information quickly when
the host takes an LPI. Call the existing injection function to let the
GIC emulation deal with this interrupt.
Signed-off-by:
