>This is the commit that test comes from. I assume you guys >would check the commit logs for something like this, but just >in case... [snippage - will just retain commit ID] >commit 5a606b72a4309a656cd1a19ad137dc5557c4b8ea Yes, this one is in. I did (and still do) suspect a hypervisor bug. I think in this case the problem is that this test is not sufficent for the "two vnets on one vswitch" case, though, because this results in the desc->status not having IRQ_INPROGRESS set on the "other" vnet that gets a double interrupt. I'm also wondering now if it has something to do with the code we added that attempts to redistribute interrupts, so that in the case of a double interrupt, the second one goes to a different CPU than the CPU already handling the first one. Although we should still see IRQ_INPROGRESS then... Chris -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
