Re: [Xen-devel] [PATCH] docs: Introduce specification for pv bootloader chainloading paths/formats.

[Ian Campbell <ijc@xxxxxxxxxxxxxx>]

On Wed, 2014-08-27 at 00:02 +0100, Colin Watson wrote:
> On Tue, Aug 26, 2014 at 07:46:58PM +0100, Ian Campbell wrote:
> > +## Protocol
> > +
> > +### x86
> > +
> > +The bootloader binary should be an ELF file of the appropriate type
> > +(32- or 64-bit). It should contain the standard Xen ELF notes allowing
> > +it to be loaded by the Xen toolstack domain builder (TBD: Reference).
> > +
> > +### ARM
> > +
> > +TBD
> > +
> > +## Paths
> > +
> > +The second stage bootloader should be installed into the guest filesystem 
> > as:
> > +
> > + * `/boot/xen/pvboot-<ARCH>.elf`
> 
> It just occurred to me that not every (future) platform may necessarily
> want this to be ELF, so maybe we shouldn't hardcode that in the
> architecture-independent part of the name.  If you think this might be a
> reasonable concern then you might want to adjust this.

This crossed my mind too (it might even be the case on arm*, not sure
yet). My thinking was that this spec would already need adjusting for
this (to describe the non-ELF thing, if nothing else) so this it could
be tweaked then too.

Or I could e.g. omit all the vestigial ARM stuff and explicitly list the
two x86 options, bypassing the whole question of future arches, who
would then need to add themselves to this doc.

>   Otherwise LGTM.
> 
> Reviewed-by: Colin Watson <cjwatson@xxxxxxxxxx>

Thanks.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel