On Thu, Jul 21, 2022, Maxim Levitsky wrote:
> On Wed, 2022-07-20 at 21:54 +0000, Sean Christopherson wrote:
> > On Sat, Jul 09, 2022, Santosh Shukla wrote:
> > > @@ -3609,6 +3612,9 @@ static void svm_enable_nmi_window(struct kvm_vcpu *vcpu)
> > > {
> > > struct vcpu_svm *svm = to_svm(vcpu);
> > >
> > > + if (is_vnmi_enabled(svm))
> > > + return;
> >
> > Ugh, is there really no way to trigger an exit when NMIs become unmasked? Because
> > if there isn't, this is broken for KVM.
> >
> > On bare metal, if two NMIs arrive "simultaneously", so long as NMIs aren't blocked,
> > the first NMI will be delivered and the second will be pended, i.e. software will
> > see both NMIs. And if that doesn't hold true, the window for a true collision is
> > really, really tiny.
> >
> > But in KVM, because a vCPU may not be run a long duration, that window becomes
> > very large. To not drop NMIs and more faithfully emulate hardware, KVM allows two
> > NMIs to be _pending_. And when that happens, KVM needs to trigger an exit when
> > NMIs become unmasked _after_ the first NMI is injected.
>
>
> This is how I see this:
>
> - When a NMI arrives and neither NMI is injected (V_NMI_PENDING) nor in service (V_NMI_MASK)
> then all it is needed to inject the NMI will be to set the V_NMI_PENDING bit and do VM entry.
>
> - If V_NMI_PENDING is set but not V_NMI_MASK, and another NMI arrives we can make the
> svm_nmi_allowed return -EBUSY which will cause immediate VM exit,
>
> and if hopefully vNMI takes priority over the fake interrupt we raise, it will be injected,
Nit (for other readers following along), it's not a fake interrupt,I would describe
it as spurious or ignored. It's very much a real IRQ, which matters because it
factors into event priority.
> and upon immediate VM exit we can inject another NMI by setting the V_NMI_PENDING again,
> and later when the guest is done with first NMI, it will take the second.
Yeaaaah. This depends heavily on the vNMI being prioritized over the IRQ.
> Of course if we get a nested exception, then it will be fun....
>
> (the patches don't do it (causing immediate VM exit),
> but I think we should make the svm_nmi_allowed, check for the case for
> V_NMI_PENDING && !V_NMI_MASK and make it return -EBUSY).
Yep, though I think there's a wrinkle (see below).
> - If both V_NMI_PENDING and V_NMI_MASK are set, then I guess we lose an NMI.
> (It means that the guest is handling an NMI, there is a pending NMI, and now
> another NMI arrived)
>
> Sean, this is the problem you mention, right?
Yep. Dropping an NMI in the last case is ok, AFAIK no CPU will pend multiple NMIs
while another is in-flight. But triggering an immediate exit in svm_nmi_allowed()
will hang the vCPU as the second pending NMI will never go away since the vCPU
won't make forward progress to unmask NMIs. This can also happen if there are
two pending NMIs and GIF=0, i.e. any time there are multiple pending NMIs and NMIs
are blocked.
One other question: what happens if software atomically sets V_NMI_PENDING while
the VMCB is in use? I assume bad things? I.e. I assume KVM can't "post" NMIs :-)
