[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <579F54B502000078001013F1@prv-mh.provo.novell.com>
Date: Mon, 01 Aug 2016 05:55:01 -0600
From: "Jan Beulich" <JBeulich@...e.com>
To: "David Vrabel" <david.vrabel@...rix.com>,
"Petr Tesarik" <PTesarik@...e.com>
Cc: "JoshTriplett" <josh@...htriplett.org>,
"maintainer:X86 ARCHITECTURE 32-BIT AND64-BIT" <x86@...nel.org>,
"ThomasGleixner" <tglx@...utronix.de>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
"open list:KEXEC" <kexec@...ts.infradead.org>,
"moderated list:XEN HYPERVISOR INTERFACE"
<xen-devel@...ts.xenproject.org>,
"Boris Ostrovsky" <boris.ostrovsky@...cle.com>,
"Dave Young" <dyoung@...hat.com>, "Ingo Molnar" <mingo@...hat.com>,
"Juergen Gross" <JGross@...e.com>,
"open list" <linux-kernel@...r.kernel.org>,
"Eric Biederman" <ebiederm@...ssion.com>,
"H.Peter Anvin" <hpa@...or.com>
Subject: Re: [Xen-devel] [PATCH 2/2] Allow kdump with
crash_kexec_post_notifiers
>>> On 13.07.16 at 14:53, <david.vrabel@...rix.com> wrote:
> 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.
For HVM guests certainly; does loading of an in-kernel crash kernel
properly fail for PV guests (and namely PV Dom0), or does such a
setup work nowadays?
Jan
Powered by blists - more mailing lists