[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MW2PR2101MB1052446D68104978CC02468FD7CE0@MW2PR2101MB1052.namprd21.prod.outlook.com>
Date: Wed, 25 Mar 2020 18:31:34 +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 3/6] x86/Hyper-V: Trigger crash enlightenment only once
during system crash.
From: Tianyu Lan <Tianyu.Lan@...rosoft.com> Sent: Tuesday, March 24, 2020 12:57 AM
>
> When a guest VM panics, Hyper-V should be notified only once via the
> crash synthetic MSRs. Current Linux code might write these crash MSRs
> twice during a system panic:
> 1) hyperv_panic/die_event() calling hyperv_report_panic()
> 2) hv_kmsg_dump() calling hyperv_report_panic_msg()
>
> Fix this by not calling hyperv_report_panic() if a kmsg dump has been
> successfully registered. The notification will happen later via
> hyperv_report_panic_msg().
>
> Signed-off-by: Tianyu Lan <Tianyu.Lan@...rosoft.com>
> ---
> Change since v1:
> - Update commit log
>
> Change since v2:
> - Update comment
> ---
> drivers/hv/vmbus_drv.c | 16 ++++++++++++++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
Reviewed-by: Michael Kelley <mikelley@...rosoft.com>
Powered by blists - more mailing lists