On Tue, Jun 16, 2015 at 04:22:12PM -0400, Joseph Salisbury wrote: > From: Nick Meier <nmeier@xxxxxxxxxxxxx> > > BugLink: http://bugs.launchpad.net/bugs/1463584 > > Hyper-V allows a guest to notify the Hyper-V host that a panic > condition occured. This notification can include up to five 64 > bit values. These 64 bit values are written into crash MSRs. > Once the data has been written into the crash MSRs, the host is > then notified by writing into a Crash Control MSR. On the Hyper-V > host, the panic notification data is captured in the Windows Event > log as a 18590 event. > > Crash MSRs are defined in appendix H of the Hypervisor Top Level > Functional Specification. At the time of this patch, v4.0 is the > current functional spec. The URL for the v4.0 document is: > > http://download.microsoft.com/download/A/B/4/AB43A34E-BDD0-4FA6-BDEF-79EEF16E880B/Hypervisor Top Level Functional Specification v4.0.docx > > Signed-off-by: Nick Meier <nmeier@xxxxxxxxxxxxx> > Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx> > Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> > (Backported from commit 96c1d0581d00f7abe033350edb021a9d947d8d81) > Signed-off-by: Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx> > --- > drivers/hv/hyperv_vmbus.h | 11 +++++++++++ > drivers/hv/vmbus_drv.c | 35 +++++++++++++++++++++++++++++++++++ > 2 files changed, 46 insertions(+) This is a new feature, why should it be added to -stable releases? Sorry, not going to take it, upgrade to 4.1 if you want this feature. greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
