On Sat, Sep 17, 2022, Sean Christopherson wrote: > The eponymous patch breaks handling of INITs (and SIPIs) that are "latched"[1] > and later become unblocked, e.g. due to entering VMX non-root mode or because SVM's > GIF is set. vmx_init_signal_test fails because KVM fails to re-evaluate pending > events after entering guest/non-root. It passes now because KVM always checks > nested events in the outer run loop. > > I have fixes, I'll (temporarily) drop this from the queue and post a new version of > this series on Monday. And by "Monday" I meant "Tuesday", the weird pending_events snapshot thing sent me down a bit of a rabbit hole.
