On 10/16/2011 11:05 AM, Jan Kiszka wrote:
> + KVM_CAP_LAPIC_NMI
> + documentation of KVM_CAP_LAPIC_NMI vs. !KVM_CAP_LAPIC_NMI
>
> So you prefer this approach over V5 / KVM_SET_LINT1? Just to make sure
> we are all looking at the full picture.
Sorry, I haven't read v5 yet (I think it wasn't downloa
On 2011-10-16 10:54, Avi Kivity wrote:
> On 10/14/2011 02:54 AM, Lai Jiangshan wrote:
>> From: Kenji Kaneshige
>>
>> Currently, NMI interrupt is blindly sent to all the vCPUs when NMI
>> button event happens. This doesn't properly emulate real hardware on
>> which NMI button event triggers LINT1.
On 10/14/2011 02:54 AM, Lai Jiangshan wrote:
> From: Kenji Kaneshige
>
> Currently, NMI interrupt is blindly sent to all the vCPUs when NMI
> button event happens. This doesn't properly emulate real hardware on
> which NMI button event triggers LINT1. Because of this, NMI is sent to
> the processo
From: Kenji Kaneshige
Currently, NMI interrupt is blindly sent to all the vCPUs when NMI
button event happens. This doesn't properly emulate real hardware on
which NMI button event triggers LINT1. Because of this, NMI is sent to
the processor even when LINT1 is maskied in LVT. For example, this
c
