Re: [PATCH] KVM: x86: Rework user space NMI injection as KVM_CAP_USER_NMI

[Avi Kivity <avi@redhat.com>]

Jan Kiszka wrote:
> There is no point in doing the ready_for_nmi_injection/
> request_nmi_window dance with user space. First, we don't do this for
> in-kernel irqchip anyway, while the code path is the same as for user
> space irqchip mode. And second, there is nothing to loose if a pending
> NMI is overwritten by another one (in contrast to IRQs where we have to
> save the number). Actually, there is even the risk of raising spurious
> NMIs this way because the reason for the held-back NMI might already be
> handled while processing the first one.
>
> Therefore this patch creates a simplified user space NMI injection
> interface, exporting it under KVM_CAP_USER_NMI and dropping the old
> KVM_CAP_NMI capability. And this time we also take care to provide the
> interface only on archs supporting NMIs via KVM (right now only x86).
>
>   

Thanks; applied, and will fold into the 2.6.29 merge.

-- 
error compiling committee.c: too many arguments to function