[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <50E6F81D02000078000B3245@nat28.tlf.novell.com>
Date: Fri, 04 Jan 2013 14:41:17 +0000
From: "Jan Beulich" <JBeulich@...e.com>
To: "Daniel Kiper" <daniel.kiper@...cle.com>
Cc: "Andrew Cooper" <andrew.cooper3@...rix.com>,
"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>,
"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>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [Xen-devel] [PATCH v3 00/11] xen: Initial kexec/kdump
implementation
>>> On 04.01.13 at 15:22, Daniel Kiper <daniel.kiper@...cle.com> wrote:
> On Wed, Jan 02, 2013 at 11:26:43AM +0000, Andrew Cooper wrote:
>> /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?
>
> This is impossible with current Xen kexec/kdump interface.
Why?
> It should be changed to do that. However, I suppose that
> Xen community would not be interested in such changes.
And again - why?
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