All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Daniel Kiper <daniel.kiper@oracle.com>,
	xen-devel <xen-devel@lists.xen.org>,
	keir@xen.org, ian.campbell@citrix.com,
	stefano.stabellini@eu.citrix.com
Subject: Re: New Xen boot infrastructure proposal
Date: Thu, 23 May 2013 07:37:58 +0100	[thread overview]
Message-ID: <519DD56602000078000D857D@nat28.tlf.novell.com> (raw)
In-Reply-To: <20130522164745.GD9712@phenom.dumpdata.com>

>>> On 22.05.13 at 18:47, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> On Wed, May 22, 2013 at 04:16:30PM +0100, Jan Beulich wrote:
>> >>> On 22.05.13 at 17:01, Daniel Kiper <daniel.kiper@oracle.com> wrote:
>> > If we stick to current MBI I am not able to pass (in sensible way),
>> > from preloader to __start_xen(), e.g. ACPI and EFI stuff from multiboot2
>> > protocol.
>> 
>> Why? You get handed a list (almost like an array) of items, and you'd
>> pass the base address instead of the base address of the multiboot
>> structure that we pass right now, together with an indicator which
>> of the two it is. Then __start_xen() has to adopt its behavior to this.
>> Not a big deal afaict.
> 
> Won't you have to do a bunch of 'if (multibootv1) { use_this_offset } else
> if (multibootv2) { use this other offset }' in the code to support
> both formats?

Yes, if this became unwieldy, I would favor the single copy approach.
Or the alternative of having the initial parts of __start_xen() split off
into two clones or prefixed by additional C code (i.e. basically the
approach the current EFI boot code is using).

Jan

  parent reply	other threads:[~2013-05-23  6:37 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 [this message]
2013-05-21 12:43 ` David Vrabel
2013-05-22 14:19   ` Daniel Kiper
2013-05-21 12:52 ` Ian Campbell
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=519DD56602000078000D857D@nat28.tlf.novell.com \
    --to=jbeulich@suse.com \
    --cc=daniel.kiper@oracle.com \
    --cc=ian.campbell@citrix.com \
    --cc=keir@xen.org \
    --cc=konrad.wilk@oracle.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --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.