WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

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

To: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>, "Xu, Anthony" <anthony.xu@xxxxxxxxx>
Subject: [Xen-ia64-devel] RE: [PATCH] Patch for loading module[2of2]
From: "Yang, Fred" <fred.yang@xxxxxxxxx>
Date: Tue, 6 Sep 2005 09:22:17 -0700
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 06 Sep 2005 16:20:06 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcWYaSAKDEpFITOYRmOMPwJnp5q9pQAADjIQADg3V1AALzs7IAAA1IBAAJG2/gAAqDjkoALc+tCgAAoHLKAAAPRkgAAApnnQAAFGaiABWEA+IAA0WXZQAACwtOAAMRIlgAAIVoZwAByzCLAAAOI5oAAQ/UWwAAWGZDAAAhkicAADG+XQABLQoxAABikZUA==
Thread-topic: [PATCH] Patch for loading module[2of2]
My suggestion as follow,

1. once it validated ok, we can put xlilo.efi (call it whatever) and
patch in the ~/tools
2. Anthony will continue to work with elilo maintainer to merge patch
into elilo after#1
3. xlilo.efi is backward compatable with elilo.efi.  We should document
xlilo usage and get users to use xlilo as much as possible
4. once patch is merged into elilo tree, we should then switch to use
one super elilo (name should be elilo.efi) as same as the native Linux.
Because we are not inventing new lilo rather adding enhancement

xlilo can also support no initrd and fully backward with elilo, so no
need for 2 lilo's

-Fred

Magenheimer, Dan (HP Labs Fort Collins) wrote:
> 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

<Prev in Thread] Current Thread [Next in Thread>