[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1357566584.7989.73.camel@zakaz.uk.xensource.com>
Date: Mon, 7 Jan 2013 13:49:44 +0000
From: Ian Campbell <Ian.Campbell@...rix.com>
To: Daniel Kiper <daniel.kiper@...cle.com>
CC: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
"H. Peter Anvin" <hpa@...or.com>,
Andrew Cooper <Andrew.Cooper3@...rix.com>,
"x86@...nel.org" <x86@...nel.org>,
"kexec@...ts.infradead.org" <kexec@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
"mingo@...hat.com" <mingo@...hat.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"Jan Beulich" <JBeulich@...e.com>,
"maxim.uvarov@...cle.com" <maxim.uvarov@...cle.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"vgoyal@...hat.com" <vgoyal@...hat.com>
Subject: Re: [Xen-devel] [PATCH v3 00/11] xen: Initial kexec/kdump
implementation
On Mon, 2013-01-07 at 12:34 +0000, Daniel Kiper wrote:
> I think that new kexec hypercall function should mimics kexec syscall.
We want to have an interface can be used by non-Linux domains (both dom0
and domU) as well though, so please bear this in mind.
Historically we've not always been good at this when the hypercall
interface is strongly tied to a particular guest implementation (in some
sense this is the problem with the current kexec hypercall).
Also what makes for a good syscall interface does not necessarily make
for a good hypercall interface.
Ian.
--
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