We will do some more tests on it to make sure there are no problems.
Wei

-----Original Message-----
From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo Bonzini
Sent: Thursday, August 28, 2014 4:44 PM
To: Zhang, Yang Z; Wang, Wei W; kvm@vger.kernel.org
Cc: alex.william...@redhat.com
Subject: Re: [PATCH v2] KVM: x86: keep eoi exit bitmap accurate before loading 
it.

Il 28/08/2014 08:17, Zhang, Yang Z ha scritto:
> >     Program edge-triggered MSI for vector 123
> >     Interrupt comes in, ISR[123]=1
> >     Mask MSI
> >     Program level-triggered IOAPIC interrupt for vector 123
> 
> You cannot assign the vector 123 to another trigger mode interrupt 
> before previous IRQ handler finished (means issue EOI). If there is an 
> interrupt comes from the IOAPIC entry immediately after you reprogram 
> the entry, it will update the TMR to 1. Since we are still in previous 
> IRQ handler, it will get confused to see the TMR becomes 1.

Yeah, that could be confusing to real hardware as well.  Still, I'm a bit 
nervous at the possibility of races introduced by these patches...

I wouldn't mind a second review.

Paolo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to