From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Kiper Subject: Re: New Xen boot infrastructure proposal Date: Wed, 22 May 2013 16:27:51 +0200 Message-ID: <20130522142751.GC25607@debian70-amd64.local.net-space.pl> References: <363082f7-72f9-41cc-a5b4-75ce235e6493@default> <1369140724.21246.62.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1369140724.21246.62.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell 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, May 21, 2013 at 01:52:04PM +0100, Ian Campbell wrote: > 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 More or less. The goal is to have one place to store info about current system config. It could be taken from different sources via various stuff (multiboot protocol, BIOS, EFI, ...) and always saved in one place. Currently all stuff is spread over various places which is not very convenient and nice. > Xen or between the early (e.g. prepaging, x86 real mode etc) Xen and > later Xen? Daniel