Re: [PATCH v3] x86/hyperv: Handle unknown NMIs on one CPU when unknown_nmi_panic

2016-12-02 Thread Vitaly Kuznetsov
Thomas Gleixner writes: > Vitaly, > > On Thu, 1 Dec 2016, Vitaly Kuznetsov wrote: > >> There is a feature in Hyper-V (Debug-VM --InjectNonMaskableInterrupt) which >> injects NMI to the guest. Prior to WS2016 the NMI is injected to all CPUs >> of the guest and WS2016 injects

Re: [PATCH v3] x86/hyperv: Handle unknown NMIs on one CPU when unknown_nmi_panic

2016-12-01 Thread Thomas Gleixner
Vitaly, On Thu, 1 Dec 2016, Vitaly Kuznetsov wrote: > There is a feature in Hyper-V (Debug-VM --InjectNonMaskableInterrupt) which > injects NMI to the guest. Prior to WS2016 the NMI is injected to all CPUs > of the guest and WS2016 injects it to CPU0 only. When unknown_nmi_panic is > enabled and

[PATCH v3] x86/hyperv: Handle unknown NMIs on one CPU when unknown_nmi_panic

2016-12-01 Thread Vitaly Kuznetsov
There is a feature in Hyper-V (Debug-VM --InjectNonMaskableInterrupt) which injects NMI to the guest. Prior to WS2016 the NMI is injected to all CPUs of the guest and WS2016 injects it to CPU0 only. When unknown_nmi_panic is enabled and we'd like to do kdump we need to perform some minimal cleanup