[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <50E55DFD02000078000B2A10@nat28.tlf.novell.com>
Date: Thu, 03 Jan 2013 09:31:25 +0000
From: "Jan Beulich" <JBeulich@...e.com>
To: "Andrew Cooper" <andrew.cooper3@...rix.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>
Cc: "x86@...nel.org" <x86@...nel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"kexec@...ts.infradead.org" <kexec@...ts.infradead.org>,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
"Daniel Kiper" <daniel.kiper@...cle.com>,
"konrad.wilk@...cle.com" <konrad.wilk@...cle.com>,
"maxim.uvarov@...cle.com" <maxim.uvarov@...cle.com>,
"mingo@...hat.com" <mingo@...hat.com>,
"vgoyal@...hat.com" <vgoyal@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"H. PeterAnvin" <hpa@...or.com>
Subject: Re: [Xen-devel] [PATCH v3 00/11] xen: Initial kexec/kdump
implementation
>>> On 02.01.13 at 12:26, Andrew Cooper <andrew.cooper3@...rix.com> wrote:
> On 27/12/12 18:02, Eric W. Biederman wrote:
>> It probably make sense to split them apart a little even.
>
> 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?
I don't think so (and suggested that before as a response to an
earlier submission of this patch set), and it would make most of
the discussion here mute.
Jan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists