[SRU][Yakkety][Zesty][PATCH 0/2] Fixes for LP:1630924

[Joseph Salisbury]

BugLink: http://bugs.launchpad.net/bugs/1630924

SRU Justification ==
Kdump through NMI SMP and single core not working on Ubuntu with Hyyper-V.
After kdump configuration, a crash is triggered through an NMI call from 
the host. The VM will panic, however it will not write the vmcore dump 
files and neither reboot.

This bug affects Vivid, Xenial, Yakkety and Zesty.  This bug is 
resolved by two patches.  The first is commit 59107e2f4, which is in
mainline as of 4.10-rc1.  The second commit, 56ef6718a1d8, is not in 
mainline as of yet, but it is in linux-next.

The patches in Yakkety and Zesting have a different context compared to Xenial
, so they will be sent as separate SRU requests.
These commits all pick cleanly in X, Y and Z.  
Vivid requires a backport, so it will be sent by itself.

== Fixes ==
commit 59107e2f48831daedc46973ce4988605ab066de3
Author: Vitaly Kuznetsov <vkuznets at redhat.com>
Date:   Fri Dec 2 11:07:20 2016 +0100

    x86/hyperv: Handle unknown NMIs on one CPU when unknown_nmi_panic

commit 56ef6718a1d8 in linux-next
Author: Vitaly Kuznetsov <vkuznets at redhat.com>
Date:   Wed Dec 7 01:16:27 2016 -0800

    hv: don't reset hv_context.tsc_page on crash


== Test Case ==
A test kernel was built with these patches and tested by the original bug reporter.
The bug reporter states the test kernel resolved the bug.

  x86/hyperv: Handle unknown NMIs on one CPU when unknown_nmi_panic
  hv: don't reset hv_context.tsc_page on crash

 arch/x86/kernel/cpu/mshyperv.c | 24 ++++++++++++++++++++++++
 drivers/hv/hv.c                |  5 +++--
 2 files changed, 27 insertions(+), 2 deletions(-)

-- 
2.7.4