Hi Eric,
On 11/08/15 10:15, Eric Auger wrote:
Hi Marc,
On 07/09/2015 03:19 PM, Marc Zyngier wrote:
So far, GICv2 has been used in with EOImode == 0. The effect of this
mode is to perform the priority drop and the deactivation of the
interrupt at the same time.
While this works perfectly
On Wed, Aug 12, 2015 at 02:31:47PM +0100, Marc Zyngier wrote:
On 11/08/15 10:15, Eric Auger wrote:
On 07/09/2015 03:19 PM, Marc Zyngier wrote:
static int gic_irq_set_irqchip_state(struct irq_data *d,
@@ -272,11 +278,15 @@ static void __exception_irq_entry
gic_handle_irq(struct pt_regs
Hi Marc,
On 07/09/2015 03:19 PM, Marc Zyngier wrote:
So far, GICv2 has been used in with EOImode == 0. The effect of this
mode is to perform the priority drop and the deactivation of the
interrupt at the same time.
While this works perfectly for Linux (we only have a single priority),
it
So far, GICv2 has been used in with EOImode == 0. The effect of this
mode is to perform the priority drop and the deactivation of the
interrupt at the same time.
While this works perfectly for Linux (we only have a single priority),
it causes issues when an interrupt is forwarded to a guest, and
