From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
Daniel Kiper <daniel.kiper@oracle.com>,
"x86@kernel.org" <x86@kernel.org>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"jbeulich@suse.com" <jbeulich@suse.com>,
"tglx@linutronix.de" <tglx@linutronix.de>
Subject: Re: [PATCH v2 01/11] kexec: introduce kexec_ops struct
Date: Thu, 22 Nov 2012 18:07:43 +0000 [thread overview]
Message-ID: <50AE69EF.4060909@citrix.com> (raw)
In-Reply-To: <50AE6542.3020302@zytor.com>
On 22/11/12 17:47, H. Peter Anvin wrote:
> The other thing that should be considered here is how utterly
> preposterous the notion of doing in-guest crash dumping is in a system
> that contains a hypervisor. The reason for kdump is that on bare metal
> there are no other options, but in a hypervisor system the right thing
> should be for the hypervisor to do the dump (possibly spawning a clean
> I/O domain if the I/O domain is necessary to access the media.)
>
> There is absolutely no reason to have a crashkernel sitting around in
> each guest, consuming memory, and possibly get corrupt.
>
> -hpa
>
I agree that regular guests should not be using the kexec/kdump.
However, this patch series is required for allowing a pvops kernel to be
a crash kernel for Xen, which is very important from dom0/Xen's point of
view.
--
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2012-11-22 18:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 15:04 [PATCH v2 00/11] xen: Initial kexec/kdump implementation Daniel Kiper
2012-11-20 15:04 ` [PATCH v2 01/11] kexec: introduce kexec_ops struct Daniel Kiper
2012-11-20 15:04 ` [PATCH v2 02/11] x86/kexec: Add extra pointers to transition page table PGD, PUD, PMD and PTE Daniel Kiper
2012-11-20 15:04 ` [PATCH v2 03/11] xen: Introduce architecture independent data for kexec/kdump Daniel Kiper
2012-11-20 15:04 ` [PATCH v2 04/11] x86/xen: Introduce architecture dependent " Daniel Kiper
2012-11-20 15:04 ` [PATCH v2 05/11] x86/xen: Register resources required by kexec-tools Daniel Kiper
2012-11-20 15:04 ` [PATCH v2 06/11] x86/xen: Add i386 kexec/kdump implementation Daniel Kiper
2012-11-20 15:04 ` [PATCH v2 07/11] x86/xen: Add x86_64 " Daniel Kiper
2012-11-20 15:04 ` [PATCH v2 08/11] x86/xen: Add kexec/kdump makefile rules Daniel Kiper
2012-11-20 15:04 ` [PATCH v2 09/11] x86/xen/enlighten: Add init and crash kexec/kdump hooks Daniel Kiper
2012-11-20 15:04 ` [PATCH v2 10/11] drivers/xen: Export vmcoreinfo through sysfs Daniel Kiper
2012-11-20 15:04 ` [PATCH v2 11/11] x86: Add Xen kexec control code size check to linker script Daniel Kiper
2012-11-20 15:52 ` [PATCH v2 02/11] x86/kexec: Add extra pointers to transition page table PGD, PUD, PMD and PTE Jan Beulich
2012-11-20 16:40 ` [PATCH v2 01/11] kexec: introduce kexec_ops struct Eric W. Biederman
2012-11-21 10:52 ` Daniel Kiper
2012-11-22 12:15 ` Eric W. Biederman
2012-11-22 17:37 ` H. Peter Anvin
2012-11-23 9:56 ` Jan Beulich
2012-11-23 10:53 ` [Xen-devel] " Ian Campbell
2012-11-22 17:47 ` H. Peter Anvin
2012-11-22 18:07 ` Andrew Cooper [this message]
2012-11-22 22:26 ` H. Peter Anvin
2014-03-31 10:50 ` Petr Tesarik
2012-11-23 0:12 ` Andrew Cooper
2012-11-23 1:34 ` H. Peter Anvin
2012-11-23 1:38 ` H. Peter Anvin
2012-11-23 1:56 ` Andrew Cooper
2012-11-23 8:01 ` Bouchard Louis
2012-11-23 9:53 ` Jan Beulich
2012-11-23 10:37 ` Daniel Kiper
2012-11-23 10:51 ` [Xen-devel] " Ian Campbell
2012-11-23 11:13 ` Daniel Kiper
2012-11-23 10:51 ` Jan Beulich
2012-11-23 11:08 ` Daniel Kiper
2012-11-23 9:47 ` Daniel Kiper
2012-11-23 20:24 ` Eric W. Biederman
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=50AE69EF.4060909@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=daniel.kiper@oracle.com \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=jbeulich@suse.com \
--cc=kexec@lists.infradead.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox