From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from smtp02.citrix.com ([66.165.176.63]) by merlin.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1TqMT9-0001OP-Ls for kexec@lists.infradead.org; Wed, 02 Jan 2013 11:26:48 +0000 Message-ID: <50E41973.9050705@citrix.com> Date: Wed, 2 Jan 2013 11:26:43 +0000 From: Andrew Cooper MIME-Version: 1.0 Subject: Re: [Xen-devel] [PATCH v3 00/11] xen: Initial kexec/kdump implementation References: <1356574740-6806-1-git-send-email-daniel.kiper@oracle.com> <50DBC856.6030208@zytor.com> <791b4922-078f-4adc-b3f3-0651f2266147@email.android.com> <50DC58C4.3000307@citrix.com> <874nj7qsor.fsf@xmission.com> In-Reply-To: <874nj7qsor.fsf@xmission.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: kexec-bounces@lists.infradead.org Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: "Eric W. Biederman" Cc: "xen-devel@lists.xensource.com" , "konrad.wilk@oracle.com" , Daniel Kiper , "x86@kernel.org" , "kexec@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "virtualization@lists.linux-foundation.org" , "mingo@redhat.com" , "jbeulich@suse.com" , "H. Peter Anvin" , "maxim.uvarov@oracle.com" , "tglx@linutronix.de" , "vgoyal@redhat.com" On 27/12/12 18:02, Eric W. Biederman wrote: > Andrew Cooper writes: > >> On 27/12/2012 07:53, Eric W. Biederman wrote: >>> The syscall ABI still has the wrong semantics. >>> >>> 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. >> There are two requirements pulling at this patch series, but I agree >> that we need to clarify them. > 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? ~Andrew _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec