From: Ian Campbell <ijc@hellion.org.uk>
To: xen-devel@lists.xen.org
Cc: 759018@bugs.debian.org, Ian Jackson <Ian.Jackson@eu.citrix.com>,
Colin Watson <cjwatson@debian.org>
Subject: Re: [PATCH v2] docs: Introduce specification for x86 pv bootloader chainloading paths/formats.
Date: Tue, 21 Oct 2014 09:17:28 +0100 [thread overview]
Message-ID: <1413879448.20604.30.camel@hellion.org.uk> (raw)
In-Reply-To: <1409343270-2375-1-git-send-email-ijc@hellion.org.uk>
On Fri, 2014-08-29 at 21:14 +0100, Ian Campbell wrote:
> In order to support pvgrub (or other bootloader) from dom0 chainloading a
> pvgrub (or other) from within the domU filesystem we need a standard for where
> the stage 1 bootloader should look and what it should expect to find there.
>
> Add a document along those lines.
>
> This is currently x86-specific since it is expected that other new architecures
> (including ARM) will either not need to implement this due to the existence of
> more generic specifications for that arch (e.g. the ARM VM spec) or will update
> this document in due course.
>
> Signed-off-by: Ian Campbell <ijc@hellion.org.uk>
> Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>
> Cc: Colin Watson <cjwatson@debian.org>
> Cc: 759018@bugs.debian.org
On IRC Ian J said:
(16:52:37) ijc: Diziet: Did you (intend to) ack <1409343270-2375-1-git-send-email-ijc@hellion.org.uk>?
(16:55:14) Diziet: ijc: I'm sure I intended to ack that, sorry.
(16:55:42) ijc: Will you or can I take the above as one?
(16:57:48) Diziet: ijc: Please do take it as an ack.
So I have fabricated an Ack and applied.
prev parent reply other threads:[~2014-10-21 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 20:14 [PATCH v2] docs: Introduce specification for x86 pv bootloader chainloading paths/formats Ian Campbell
2014-10-21 8:17 ` 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=1413879448.20604.30.camel@hellion.org.uk \
--to=ijc@hellion.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).