On Thu, Aug 30, 2018 at 12:57:32PM +0300, Liran Alon wrote: > Consider the case L1 had a IRQ/NMI event until it executed > VMLAUNCH/VMRESUME which wasn't delivered because it was disallowed > (e.g. interrupts disabled). When L1 executes VMLAUNCH/VMRESUME, > L0 needs to evaluate if this pending event should cause an exit from > L2 to L1 or delivered directly to L2 (e.g. In case L1 don't intercept > EXTERNAL_INTERRUPT). > > Usually this would be handled by L0 requesting a IRQ/NMI window > by setting VMCS accordingly. However, this setting was done on > VMCS01 and now VMCS02 is active instead. Thus, when L1 executes > VMLAUNCH/VMRESUME we force L0 to perform pending event evaluation by > requesting a KVM_REQ_EVENT. > > Note that above scenario exists when L1 KVM is about to enter L2 but > requests an "immediate-exit". As in this case, L1 will > disable-interrupts and then send a self-IPI before entering L2. > > Co-authored-by: Sean Christopherson <sean.j.christopherson@xxxxxxxxx> The tag you're looking for is "Co-developed-by" and requires my sob. Thanks for the recognition! Documentation/process/5.Posting.rst: - Co-developed-by: states that the patch was also created by another developer along with the original author. This is useful at times when multiple people work on a single patch. Note, this person also needs to have a Signed-off-by: line in the patch as well. Without further ado: Signed-off-by: Sean Christopherson <sean.j.christopherson@xxxxxxxxx> > Signed-off-by: Liran Alon <liran.alon@xxxxxxxxxx>
