From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: New Xen boot infrastructure proposal
Date: Tue, 21 May 2013 13:52:04 +0100
Message-ID: <1369140724.21246.62.camel@zakaz.uk.xensource.com>
References: <363082f7-72f9-41cc-a5b4-75ce235e6493@default>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <363082f7-72f9-41cc-a5b4-75ce235e6493@default>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Daniel Kiper <daniel.kiper@oracle.com>
Cc: xen-devel@lists.xensource.com, keir@xen.org, jbeulich@suse.com, stefano.stabellini@eu.citrix.com, konrad.wilk@oracle.com
List-Id: xen-devel@lists.xenproject.org

On Tue, 2013-05-21 at 03:36 -0700, Daniel Kiper wrote:
> It means
> that at this stage it is worth to create completely new
> boot structure which is not linked so tightly with any boot
> protocol. It should contain all needed stuff, be architecture
> independent as much as possible and easily extensible.

Is this proposal intended to form a protocol between the bootloader and
Xen or between the early (e.g. prepaging, x86 real mode etc) Xen and
later Xen?

Ian.