Re: [Xen-devel] New Xen boot infrastructure proposal

[Daniel Kiper <daniel.kiper@xxxxxxxxxx>]

On Wed, May 22, 2013 at 03:33:29PM +0100, Jan Beulich wrote:
> >>> On 22.05.13 at 16:09, Daniel Kiper <daniel.kiper@xxxxxxxxxx> wrote:

[...]

> > I think that passing info about system via many not "linked" variables
> > is not the best idea. It works in that way today because multiboot
> > structure is not extensible. That is why I think we should find new
> > solution. Our new custom build structure which contains only stuff
> > required by Xen looks good. All members are easliy accessible from C.
> > It could be easliy extended (if we need it just add new member) because
> > it would not be linked with specific boot protocol.
>
> Why does  it matter whether the MBI structure is extensible?

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. That is why I think we should build our own struct which is not
linked with any boot protocol. That way we could avoid similar problems
in the future.

> Rather than copying everything around a number of times, we
> can as well use is where it lives naturally. The only requirement

This is the best approach if we would have one type of boot protocol.
It is not true if we would like to support more then one.

> is that all information be accessible - whether in one strcture,
> two, or a dozen doesn't matter.

I agree that this is not a must but I prefer to have "all in one" :-)))...
We could do that cleanups (by the way) if we decide what to do with above 
issues.

Daniel

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