All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Colin Watson <cjwatson@debian.org>
Cc: 759018@bugs.debian.org, Ian Jackson <Ian.Jackson@eu.citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH] docs: Introduce specification for pv bootloader chainloading paths/formats.
Date: Fri, 29 Aug 2014 01:44:59 +0100	[thread overview]
Message-ID: <1409273099.21481.61.camel@citrix.com> (raw)
In-Reply-To: <1409094994.28009.58.camel@hellion.org.uk>

On Wed, 2014-08-27 at 00:16 +0100, Ian Campbell wrote:
> > 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.

While talking to Colin IRL a couple of nights ago I realised that this
stuff is most likely more specific to x86 PV than I had originally
thought. ARM for example is far more likely to follow the ARM VM spec[0]
and use a UEFI firmware as the stage 1 and the EFI bootprotocol to find
and execute the stage 2 (e.g. grub.efi from the ESP). And who knows what
any future arches might do.

So I intend to update the doc to be less arch agnostic and make it just
cover x86. If some future arch wants something along these lines then
they would have to patch this spec anyway.

Ian.

[0]
http://lists.linaro.org/pipermail/cross-distro/2014-March/000668.html
> 
> >   Otherwise LGTM.
> > 
> > Reviewed-by: Colin Watson <cjwatson@debian.org>
> 
> Thanks.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

      reply	other threads:[~2014-08-29  0:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 18:46 [PATCH] docs: Introduce specification for pv bootloader chainloading paths/formats Ian Campbell
2014-08-26 21:45 ` Don Slutz
2014-08-26 23:02 ` Colin Watson
2014-08-26 23:16   ` Ian Campbell
2014-08-29  0:44     ` Ian Campbell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1409273099.21481.61.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=759018@bugs.debian.org \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=cjwatson@debian.org \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.