[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <578639AE.10500@citrix.com>
Date: Wed, 13 Jul 2016 13:53:02 +0100
From: David Vrabel <david.vrabel@...rix.com>
To: Petr Tesarik <ptesarik@...e.com>, Juergen Gross <jgross@...e.com>,
"Josh Triplett" <josh@...htriplett.org>,
Ingo Molnar <mingo@...hat.com>,
"Thomas Gleixner" <tglx@...utronix.de>,
Eric Biederman <ebiederm@...ssion.com>,
"H. Peter Anvin" <hpa@...or.com>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Dave Young <dyoung@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
David Vrabel <david.vrabel@...rix.com>
CC: "moderated list:XEN HYPERVISOR INTERFACE"
<xen-devel@...ts.xenproject.org>,
"maintainer:X86 ARCHITECTURE 32-BIT AND 64-BIT" <x86@...nel.org>,
"open list:KEXEC" <kexec@...ts.infradead.org>,
"open list" <linux-kernel@...r.kernel.org>
Subject: Re: [Xen-devel] [PATCH 2/2] Allow kdump with
crash_kexec_post_notifiers
On 13/07/16 13:20, Petr Tesarik wrote:
> If a crash kernel is loaded, do not crash the running domain. This is
> needed if the kernel is loaded with crash_kexec_post_notifiers, because
> panic notifiers are run before __crash_kexec() in that case, and this
> Xen hook prevents its being called later.
Prioritising the in-kernel kexec image over the hypervisor one seems
sensible behaviour to me.
Reviewed-by: David Vrabel <david.vrabel@...rix.com>
David
Powered by blists - more mailing lists