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: "Xu, Anthony" <anthony.xu@xxxxxxxxx>, "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>
Subject: [Xen-ia64-devel] RE: [PATCH] Patch for loading module[2of2]
From: "Yang, Fred" <fred.yang@xxxxxxxxx>
Date: Mon, 5 Sep 2005 19:42:38 -0700
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 06 Sep 2005 02:40:26 +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/UWwAAWGZDAAAd3zQA==
Thread-topic: [PATCH] Patch for loading module[2of2]
Xu, Anthony wrote:
>>> Using initrd to load Linux kernel image is only a temporally
>>> workround and should be corrected.  There is no backward
>>> compability issue on Xen/ia64 on loading kernel image per se.
>>>  Rather, "initrd" should be maintained to load "initrd"
>>> maintains the backward compability with current elilo.efi.
>>> The "module" add-on is to continue to maintain elilo compability
>>> Imaging a single elilo.conf to have multi-initrd with two
>>> different meanings, this is definitely to confuse users.
>> 
>> I suppose that's a reasonable argument, though I don't agree
>> that your changed parameter names are any less confusing than
>> the original way: "module" is hardly a parameter name for the
>> domain0 image. 
>> 
>> Maybe the right answer is for elilo to allow a "domain0="
>> parameter name, which could be an alias for "module=".
>> I'm not sure the elilo maintainers would like that,
>> but it would certainly be the least confusing alternative.
>> 
>> This might be a good topic for a poll... we now have over
>> 70 people on this list.  Let's ask (see next message).
>> 
> 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.  

FYI, xen/x86 is also using module, a GRUB feature, to load Linux kernel
image.

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