Re: [RESEND PATCH 5/6] KVM: x86/VMX: add kvm_vmx_reinject_nmi_irq() for NMI/IRQ reinjection

Peter Zijlstra
2022-11-11T09:15:37Z

On Thu, Nov 10, 2022 at 08:53:30PM +0000, Li, Xin3 wrote:

> > > static void handle_external_interrupt_irqoff(struct kvm_vcpu *vcpu)
> > > {
> > > u32 intr_info = vmx_get_intr_info(vcpu);
> > > unsigned int vector = intr_info & INTR_INFO_VECTOR_MASK;
> > > - gate_desc *desc = (gate_desc *)host_idt_base + vector;
> > >
> > > if (KVM_BUG(!is_external_intr(intr_info), vcpu->kvm,
> > > "KVM: unexpected VM-Exit interrupt info: 0x%x", intr_info))
> > > return;
> > >
> > > - handle_interrupt_nmi_irqoff(vcpu, gate_offset(desc));
> > > + handle_interrupt_nmi_irqoff(vcpu, vector);
> > > vcpu->arch.at_instruction_boundary = true; }
> >
> > How does any of this work? You're calling into entry/noinstr code from a
> > random context.
>
> Can you please elaborate your concern a bit more?
>
> We are here in handle_external_interrupt_irqoff () because an external
> interrupt happened when a guest was running and the CPU vm-exits to host
> to dispatch to the IRQ handler with IRQ disabled.

I don't speak virt (but this all sounds disguisting) -- but what appears
to be the case is you calling into entry code from regular kernel
context, which is odd at best.

Specifically, going by the fact that all this is not noinstr code, the
assumption is that RCU/lockdep/etc.. is all set-up and running. This
means you should not be calling DEFINE_IDTENTRY_*(func) functions
because those will try and set all that up again.

Granted, irqentry_{enter,exit}() do nest, but *yuck*.