[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200330101331.v4yahaqszgbo27km@debian>
Date: Mon, 30 Mar 2020 11:13:31 +0100
From: Wei Liu <wei.liu@...nel.org>
To: ltykernel@...il.com
Cc: kys@...rosoft.com, haiyangz@...rosoft.com, sthemmin@...rosoft.com,
liuwe@...rosoft.com, tglx@...utronix.de, mingo@...hat.com,
bp@...en8.de, hpa@...or.com, x86@...nel.org,
michael.h.kelley@...rosoft.com,
Tianyu Lan <Tianyu.Lan@...rosoft.com>,
linux-hyperv@...r.kernel.org, linux-kernel@...r.kernel.org,
vkuznets@...hat.com, Wei Liu <wei.liu@...nel.org>
Subject: Re: [PATCH V3 0/6] x86/Hyper-V: Panic code path fixes
On Tue, Mar 24, 2020 at 12:57:14AM -0700, ltykernel@...il.com wrote:
> From: Tianyu Lan <Tianyu.Lan@...rosoft.com>
>
> This patchset fixes some issues in the Hyper-V panic code path.
> Patch 1 resolves issue that panic system still responses network
> packets.
> Patch 2-3,5-6 resolves crash enlightenment issues.
> Patch 4 is to set crash_kexec_post_notifiers to true for Hyper-V
> VM in order to report crash data or kmsg to host before running
> kdump kernel.
>
> Tianyu Lan (6):
> x86/Hyper-V: Unload vmbus channel in hv panic callback
> x86/Hyper-V: Free hv_panic_page when fail to register kmsg dump
> x86/Hyper-V: Trigger crash enlightenment only once during system
> crash.
> x86/Hyper-V: Report crash register data or ksmg before running crash
> kernel
> x86/Hyper-V: Report crash register data when sysctl_record_panic_msg
> is not set
> x86/Hyper-V: Report crash data in die() when panic_on_oops is set
>
Queued to hyperv-next. Thanks.
Wei.
Powered by blists - more mailing lists