On Mon, May 11, 2015 at 04:00:03PM +0200, Ingo Molnar wrote: > > So potentially, CPU0 generated an interrupt that caused > > vcpu_enter_guest to be called on CPU1. However, when > > vmx_handle_external_intr was called, it didn't progress any further. > > So the IPI does look like to be lost in the KVM code? > > So why did vmx_handle_external_intr() skip the irq injection - were > IRQs disabled in the guest perhaps? > > > Another experiment here would be to dump > > vmcs_read32(VM_EXIT_INTR_INFO); to see why we don't handle the > > interrupt. > > Possibly, but also to instrument the KVM IRQ injection code to see > when it skips an IPI and why. > > Thanks, > > Ingo >
Ingo, I no longer have access to the reproducer machine unfortunately. I'll try to locate additional kit that has the same situation, but it may take some time. Thanks, --chris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
