From: Ian Campbell <Ian.Campbell@citrix.com>
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
Subject: Re: New Xen boot infrastructure proposal
Date: Tue, 21 May 2013 13:52:04 +0100 [thread overview]
Message-ID: <1369140724.21246.62.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <363082f7-72f9-41cc-a5b4-75ce235e6493@default>
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.
next prev parent reply other threads:[~2013-05-21 12:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 10:36 New Xen boot infrastructure proposal Daniel Kiper
2013-05-21 11:39 ` Stefano Stabellini
2013-05-21 12:57 ` Daniel Kiper
2013-05-21 12:03 ` Jan Beulich
2013-05-22 14:09 ` Daniel Kiper
2013-05-22 14:33 ` Jan Beulich
2013-05-22 15:01 ` Daniel Kiper
2013-05-22 15:16 ` Jan Beulich
2013-05-22 16:47 ` Konrad Rzeszutek Wilk
2013-05-22 16:56 ` Keir Fraser
2013-05-23 6:37 ` Jan Beulich
2013-05-21 12:43 ` David Vrabel
2013-05-22 14:19 ` Daniel Kiper
2013-05-21 12:52 ` Ian Campbell [this message]
2013-05-22 14:27 ` Daniel Kiper
2013-05-22 14:35 ` Jan Beulich
2013-05-22 15:09 ` Ian Campbell
2013-05-22 15:25 ` Ian Campbell
2013-05-22 15:34 ` Daniel Kiper
2013-05-22 15:41 ` Ian Campbell
2013-05-22 16:19 ` Daniel Kiper
2013-05-23 13:33 ` Ian Campbell
2013-05-21 13:24 ` Keir Fraser
2013-05-22 14:43 ` Daniel Kiper
2013-05-22 15:10 ` Jan Beulich
2013-05-22 15:59 ` Daniel Kiper
2013-05-22 16:40 ` Keir Fraser
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=1369140724.21246.62.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=daniel.kiper@oracle.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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.