From: David Vrabel <david.vrabel@citrix.com>
To: Petr Tesarik <ptesarik@suse.com>, Juergen Gross <jgross@suse.com>,
Josh Triplett <josh@joshtriplett.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Eric Biederman <ebiederm@xmission.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Dave Young <dyoung@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Vrabel <david.vrabel@citrix.com>
Cc: "moderated list:XEN HYPERVISOR INTERFACE"
<xen-devel@lists.xenproject.org>,
"maintainer:X86 ARCHITECTURE 32-BIT AND 64-BIT" <x86@kernel.org>,
"open list:KEXEC" <kexec@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH 2/2] Allow kdump with crash_kexec_post_notifiers
Date: Wed, 13 Jul 2016 13:53:02 +0100 [thread overview]
Message-ID: <578639AE.10500@citrix.com> (raw)
In-Reply-To: <20160713122000.14969.99963.stgit@hananiah.suse.cz>
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@citrix.com>
David
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: David Vrabel <david.vrabel@citrix.com>
To: Petr Tesarik <ptesarik@suse.com>, Juergen Gross <jgross@suse.com>,
"Josh Triplett" <josh@joshtriplett.org>,
Ingo Molnar <mingo@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
Eric Biederman <ebiederm@xmission.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Dave Young <dyoung@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Vrabel <david.vrabel@citrix.com>
Cc: "moderated list:XEN HYPERVISOR INTERFACE"
<xen-devel@lists.xenproject.org>,
"maintainer:X86 ARCHITECTURE 32-BIT AND 64-BIT" <x86@kernel.org>,
"open list:KEXEC" <kexec@lists.infradead.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH 2/2] Allow kdump with crash_kexec_post_notifiers
Date: Wed, 13 Jul 2016 13:53:02 +0100 [thread overview]
Message-ID: <578639AE.10500@citrix.com> (raw)
In-Reply-To: <20160713122000.14969.99963.stgit@hananiah.suse.cz>
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@citrix.com>
David
next prev parent reply other threads:[~2016-07-13 12:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 12:19 [PATCH 0/2] Allow crash dumps with crash_kexec_post_notifiers Petr Tesarik
2016-07-13 12:19 ` Petr Tesarik
2016-07-13 12:19 ` [PATCH 1/2] Add a kexec_crash_loaded() function Petr Tesarik
2016-07-13 12:19 ` Petr Tesarik
2016-07-13 12:52 ` Josh Triplett
2016-07-13 12:52 ` Josh Triplett
2016-07-13 13:03 ` Petr Tesarik
2016-07-13 13:03 ` Petr Tesarik
2016-07-13 13:03 ` Petr Tesarik
2016-07-13 12:52 ` Josh Triplett
2016-07-13 12:19 ` Petr Tesarik
2016-07-13 12:20 ` [PATCH 2/2] Allow kdump with crash_kexec_post_notifiers Petr Tesarik
2016-07-13 12:20 ` Petr Tesarik
2016-07-13 12:20 ` Petr Tesarik
2016-07-13 12:53 ` David Vrabel [this message]
2016-07-13 12:53 ` [Xen-devel] " David Vrabel
2016-08-01 11:55 ` Jan Beulich
2016-08-01 11:55 ` [Xen-devel] " Jan Beulich
2016-08-01 11:55 ` Jan Beulich
[not found] ` <579F54B502000078001013F1@suse.com>
2016-08-01 13:02 ` Petr Tesarik
2016-08-01 13:47 ` Jan Beulich
[not found] ` <579F6F2E0200007800101563@suse.com>
2016-08-01 14:15 ` Petr Tesarik
2016-08-01 14:22 ` Jan Beulich
2016-08-01 14:25 ` Konrad Rzeszutek Wilk
2016-08-03 17:55 ` Daniel Kiper
[not found] ` <579F773A02000078001015C1@suse.com>
2016-08-01 15:17 ` Petr Tesarik
2016-07-13 12:53 ` David Vrabel
2016-07-13 12:27 ` [PATCH 0/2] Allow crash dumps " Petr Tesarik
2016-07-13 12:27 ` Petr Tesarik
2016-07-13 12:27 ` Petr Tesarik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=578639AE.10500@citrix.com \
--to=david.vrabel@citrix.com \
--cc=akpm@linux-foundation.org \
--cc=boris.ostrovsky@oracle.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=josh@joshtriplett.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=ptesarik@suse.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.