From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756211AbcAYKac (ORCPT ); Mon, 25 Jan 2016 05:30:32 -0500 Received: from mail-wm0-f67.google.com ([74.125.82.67]:36285 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753830AbcAYKaa (ORCPT ); Mon, 25 Jan 2016 05:30:30 -0500 Subject: Re: [Xen-devel] [PATCH v1 04/12] xen/hvmlite: Bootstrap HVMlite guest To: Konrad Rzeszutek Wilk , "H. Peter Anvin" , Andrew Cooper , "Luis R. Rodriguez" References: <1453498558-6028-1-git-send-email-boris.ostrovsky@oracle.com> <1453498558-6028-5-git-send-email-boris.ostrovsky@oracle.com> <20160122233218.GA20964@wotan.suse.de> <56A2C99A.2050701@citrix.com> <56A39300.8050802@citrix.com> <6012806F-E377-4444-9925-AA64210081E4@oracle.com> Cc: Juergen Gross , Jeremy Fitzhardinge , Rusty Russell , "linux-kernel@vger.kernel.org" , Andy Lutomirski , David Vrabel , xen-devel@lists.xenproject.org, Boris Ostrovsky , Borislav Petkov From: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= X-Enigmail-Draft-Status: N1110 Message-ID: <56A5F941.4070502@FreeBSD.org> Date: Mon, 25 Jan 2016 11:30:25 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org El 23/01/16 a les 17.12, Konrad Rzeszutek Wilk ha escrit: > On January 23, 2016 11:01:06 AM EST, "H. Peter Anvin" wrote: >> On January 23, 2016 7:34:33 AM PST, Konrad Rzeszutek Wilk >> wrote: >>> >>>> However, this stub belongs in Linux, not in the Xen toolstack. That >>>> way, when the Linux boot protocol is modified, both sides can be >>>> updated >>>> accordingly. >>> >>> I would add that this idea is borrowed from the EFI stub code that >>> Linux has which also constructs the boot parameter structure when >>> invoked (either from firmware or from EFI shell). >> >> There is a huge difference though: EFI is a widely used multivendor >> industry standard. You are taking about something Xen-specific, and >> which in good Xen tradition isn't even documented, apparently (did we >> ever get documentation for the hypervisor ABI?) >> >> Asking "why burden Xen with something Linux-specific" is a pretty >> extreme case of the tail wagging the dog. >> >> That being said, before any code can be put anywhere, it needs to be >> written. We can argue where to put it later. We went through this >> process with the EFI stub, too: a standalone implementation (efilinux) >> first. > > http://lists.xenproject.org/archives/html/xen-devel/2015-12/msg01793.html > > I believe is the latest version. Roger (CCed) has probably an updated one. Yes, the technical side has not changed at all. I've just send an updated version with some wording changes: http://lists.xenproject.org/archives/html/xen-devel/2016-01/msg03029.html Roger.