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

Re: [Xen-devel] [PATCH] xen/arm: introduce platform_need_explicit_eoi

Hi Stefano,

On 20/06/14 14:35, Stefano Stabellini wrote:
GICH_LR_HW doesn't work as expected on X-Gene: request maintenance
interrupts and perform EOIs in the hypervisor as a workaround.
Trigger this behaviour with a per platform option.

No need to find the pcpu that needs to write to GICC_DIR, because after
"physical irq follow virtual irq" we always inject the virtual irq on
the vcpu that is running on the pcpu that received the interrupt.

Even without the patch "physical irq follow virtual irq" we can EOI an SPIs on any physical CPUs.

Otherwise, even with this patch, you will have to find pcpu when the VCPU has been migrated by EOI the IRQ :).

I would rework this last paragraph to explain this is how the GIC behave.

  static void gic_update_one_lr(struct vcpu *v, int i)
      struct pending_irq *p;
@@ -692,7 +699,11 @@ static void gic_update_one_lr(struct vcpu *v, int i)
          clear_bit(i, &this_cpu(lr_mask));

          if ( p->desc != NULL )
+        {
              p->desc->status &= ~IRQ_INPROGRESS;
+            if ( platform_has_quirk(PLATFORM_QUIRK_NEED_EOI) )
+                gic_irq_eoi(p->irq);
+        }
          clear_bit(GIC_IRQ_GUEST_VISIBLE, &p->status);
          clear_bit(GIC_IRQ_GUEST_ACTIVE, &p->status);
          p->lr = GIC_INVALID_LR;

With this change, shouldn't we clear the bit and the LR before EOI the IRQ?


Julien Grall

Xen-devel mailing list



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