Re: [Xen-devel] [PATCH v3 00/11] xen: Initial kexec/kdump implementation
From: Andrew Cooper
Date: Wed Jan 02 2013 - 06:26:35 EST
On 27/12/12 18:02, Eric W. Biederman wrote:
Andrew Cooper<andrew.cooper3@xxxxxxxxxx> writes:
On 27/12/2012 07:53, Eric W. Biederman wrote:
It probably make sense to split them apart a little even.
The syscall ABI still has the wrong semantics.There are two requirements pulling at this patch series, but I agree
Aka totally unmaintainable and umergeable.
The concept of domU support is also strange. What does domU support even mean, when the dom0 support is loading a kernel to pick up Xen when Xen falls over.
that we need to clarify them.
Thinking about this split, there might be a way to simply it even more.
/sbin/kexec can load the "Xen" crash kernel itself by issuing hypercalls
using /dev/xen/privcmd. This would remove the need for the dom0 kernel
to distinguish between loading a crash kernel for itself and loading a
kernel for Xen.
Or is this just a silly idea complicating the matter?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/