> From: Tian, Kevin > Sent: Wednesday, May 25, 2011 4:40 PM > > If L1 turns on VM_EXIT_ACK_INTR_ON_EXIT (again, no hypervisor that I know > > does), things look very different from the description above: L1 expects > > Type-1 bare metal hypervisor may enable this bit, such as Xen. This bit is > really prepared for L2 hypervisor since normally L2 hypervisor is tricky to > touch generic interrupt logic, and thus better to not ack it until interrupt > is enabled and then hardware will gear to the kernel interrupt handler > automatically. > > > to see an exit from L2 with the interrupt vector already filled in the exit > > information, and does not expect to be interrupted again with this interrupt. > > The current code does not (yet) support this case, so we do not allow the > > VM_EXIT_ACK_INTR_ON_EXIT exit-control to be turned on by L1. > > Then just fill the interrupt vector field with the highest unmasked bit > from pending vIRR. > And also ack virtual irqchip accordingly... Thanks Kevin -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
