[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MW2PR2101MB1052302CA7C500F727DF6C92D7CE0@MW2PR2101MB1052.namprd21.prod.outlook.com>
Date: Wed, 25 Mar 2020 18:33:26 +0000
From: Michael Kelley <mikelley@...rosoft.com>
To: "ltykernel@...il.com" <ltykernel@...il.com>,
KY Srinivasan <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
Wei Liu <liuwe@...rosoft.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"bp@...en8.de" <bp@...en8.de>, "hpa@...or.com" <hpa@...or.com>,
"x86@...nel.org" <x86@...nel.org>
CC: Tianyu Lan <Tianyu.Lan@...rosoft.com>,
"linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
vkuznets <vkuznets@...hat.com>
Subject: RE: [PATCH V3 4/6] x86/Hyper-V: Report crash register data or ksmg
before running crash kernel
From: Tianyu Lan <Tianyu.Lan@...rosoft.com> Sent: Tuesday, March 24, 2020 12:57 AM
>
> We want to notify Hyper-V when a Linux guest VM crash occurs, so
> there is a record of the crash even when kdump is enabled. But
> crash_kexec_post_notifiers defaults to "false", so the kdump kernel
> runs before the notifiers and Hyper-V never gets notified. Fix this by
> always setting crash_kexec_post_notifiers to be true for Hyper-V VMs.
>
> Signed-off-by: Tianyu Lan <Tianyu.Lan@...rosoft.com>
> ---
> Change since v1:
> Update commit log
> ---
> arch/x86/kernel/cpu/mshyperv.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
Reviewed-by: Michael Kelley <mikelley@...rosoft.com>
Powered by blists - more mailing lists