Messages in this thread | | | From | Vitaly Kuznetsov <> | Subject | Re: [PATCH v2] x86/hyperv: Handle unknown NMIs on one CPU when unknown_nmi_panic | Date | Thu, 01 Dec 2016 17:10:49 +0100 |
| |
Vitaly Kuznetsov <vkuznets@redhat.com> writes:
[snip]
> static void __init ms_hyperv_init_platform(void) > { > /* > @@ -183,6 +204,9 @@ static void __init ms_hyperv_init_platform(void) > pr_info("HyperV: LAPIC Timer Frequency: %#x\n", > lapic_timer_frequency); > } > + > + register_nmi_handler(NMI_LOCAL, hv_nmi_unknown, NMI_FLAG_FIRST, > + "hv_nmi_unknown");
This should probably be NMI_UNKNOWN instead of NMI_LOCAL. While it works regardless and we don't have other NMIs on Hyper-V VMs (or do we?) I think it would be better to do v3.
Sorry for the inconvenience.
-- Vitaly
| |