On Mon, Nov 02, 2015 at 01:16:02PM +0100, Paolo Bonzini wrote: > On 26/10/2015 10:56, Andrey Smetanin wrote: > > Hyper-V SynIC is a Hyper-V synthetic interrupt controller. > > > > The test runs on every vCPU and performs the following steps: > > * read from all Hyper-V SynIC MSR's > > * setup Hyper-V SynIC evt/msg pages > > * setup SINT's routing > > * inject SINT's into destination vCPU by 'hyperv-synic-test-device' > > * wait for SINT's isr's completion > > * clear Hyper-V SynIC evt/msg pages and destroy SINT's routing > > > > Signed-off-by: Andrey Smetanin <asmetanin@xxxxxxxxxxxxx> > > Reviewed-by: Roman Kagan <rkagan@xxxxxxxxxxxxx> > > Signed-off-by: Denis V. Lunev <den@xxxxxxxxxx> > > CC: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx> > > CC: "K. Y. Srinivasan" <kys@xxxxxxxxxxxxx> > > CC: Gleb Natapov <gleb@xxxxxxxxxx> > > CC: Paolo Bonzini <pbonzini@xxxxxxxxxx> > > CC: Roman Kagan <rkagan@xxxxxxxxxxxxx> > > CC: Denis V. Lunev <den@xxxxxxxxxx> > > CC: qemu-devel@xxxxxxxxxx > > CC: virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx > > Bad news. > > The test breaks with APICv, because of the following sequence of events: Thanks for testing and analyzing this! (... running around looking for an APICv-capable machine to be able to catch this ourselves before we resubmit ...) > The question then is... does Hyper-V actually use auto-EOI interrupts? > If it doesn't, we might as well not implement them... :/ As Den wrote, we've yet to see a hyperv device which doesn't :( Roman. -- 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
