Vitaly Kuznetsov 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);
> }
> +
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
