From: Greg KH <gregkh@linuxfoundation.org>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: luis.henriques@canonical.com, kamal.mostafa@canonical.com,
sasha.levin@oracle.com, fengguang.wu@intel.com,
haiyangz@microsoft.com, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, nmeier@microsoft.com,
devel@linuxdriverproject.org
Subject: Re: [v3.16.y-ckt][v3.18.y][v3.19.y-ckt][v4.0.y][PATCH 1/1]Drivers: hv: vmbus: Add support for VMBus panic notifier handler
Date: Fri, 26 Jun 2015 17:47:36 -0700 [thread overview]
Message-ID: <20150627004736.GA29233@kroah.com> (raw)
In-Reply-To: <9b0a0ca030da9741fb0ad6f41147a99ac7a21fdd.1434395983.git.joseph.salisbury@canonical.com>
On Tue, Jun 16, 2015 at 04:22:12PM -0400, Joseph Salisbury wrote:
> From: Nick Meier <nmeier@microsoft.com>
>
> 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@microsoft.com>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> (Backported from commit 96c1d0581d00f7abe033350edb021a9d947d8d81)
> Signed-off-by: Joseph Salisbury <joseph.salisbury@canonical.com>
> ---
> 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
next prev parent reply other threads:[~2015-06-27 0:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 20:04 [3.13.y-ckt][PATCH 0/1][Hyper-V] Add support for VMBus panic notifier handler Joseph Salisbury
2015-06-16 20:04 ` [3.13.y-ckt][PATCH 1/1] Drivers: hv: vmbus: " Joseph Salisbury
[not found] ` <cover.1434395983.git.joseph.salisbury@canonical.com>
2015-06-16 20:22 ` [v3.16.y-ckt][v3.18.y][v3.19.y-ckt][v4.0.y][PATCH 1/1]Drivers: " Joseph Salisbury
2015-06-27 0:47 ` Greg KH [this message]
2015-06-30 15:20 ` Kamal Mostafa
[not found] ` <cover.1434486527.git.joseph.salisbury@canonical.com>
2015-06-16 20:31 ` [v3.14.y][PATCH 1/1] Drivers: " Joseph Salisbury
2015-06-16 20:39 ` Greg KH
2015-06-16 20:41 ` [3.13.y-ckt][PATCH 0/1][Hyper-V] " Greg KH
2015-06-16 20:49 ` Joseph Salisbury
2015-06-17 14:50 ` [v3.16.y-ckt][v3.18.y][v3.19.y-ckt][v4.0.y][PATCH " Luis Henriques
2015-06-17 18:22 ` Kamal Mostafa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150627004736.GA29233@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@linuxdriverproject.org \
--cc=fengguang.wu@intel.com \
--cc=haiyangz@microsoft.com \
--cc=joseph.salisbury@canonical.com \
--cc=kamal.mostafa@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.henriques@canonical.com \
--cc=nmeier@microsoft.com \
--cc=sasha.levin@oracle.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox