On Tue, Jun 16, 2015 at 04:31:38PM -0400, Joseph Salisbury wrote: > From: Nick Meier <nmeier@xxxxxxxxxxxxx> > > > 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> > > Conflicts: > drivers/hv/vmbus_drv.c What are these two lines doing here? Please remove and resend. Also, what about 4.0 and other kernels, should this patch go there as well? If so, just say "please add commit id XXXXXX to these kernels", that's all that is needed if no patch changes are required. thanks, greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
