[Xen-ia64-devel] RE: [PATCH] Patch for loading module[2of2]

["Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>]

On a related note:  Is there any reason that we shouldn't
just package the modified elilo.efi binary in
xen/arch/ia64/tools/elilo/xenelilo.efi?  It would be
nasty to force every user to rebuild the modified
elilo.efi with all those patches.

Call it xenelilo.efi to ensure that users don't
get confused; the Xen/ia64 docs should specify that users
install and use xenelilo.efi, with a footnote that says
that the new functionality in xenelilo.efi will eventually
be absorbed into a future elilo.efo and that the old/current
elilo.efi can be used only if no initrd is neded.

Dan

> -----Original Message-----
> From: Xu, Anthony [mailto:anthony.xu@xxxxxxxxx] 
> Sent: Monday, September 05, 2005 10:19 PM
> To: Magenheimer, Dan (HP Labs Fort Collins); Yang, Fred
> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [PATCH] Patch for loading module[2of2]
> 
> >> Elilo is a gerernal OS loader,it doesn't and doesn't need to
> >> know presence of domain0,
> >> For elilo, xen.gz is a OS kernel, initrd= it's Os's initial
> >> ramdisk, module= is Os's parameter, we should keep all this
> >> meaning, we shouldn't make elilo special just for xen.
> >
> >Yes, module= is OS's parameter, but domain0 is not
> >really a parameter.
> From the view of Elilo, xen is an OS, domain0 is a parameter to xen.
> As far as how to handle this parameter, it's up to xen.
> 

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel