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-devel

Re: [Xen-devel] behavioral change due to new elf code

To: "Gerd Hoffmann" <kraxel@xxxxxxx>
Subject: Re: [Xen-devel] behavioral change due to new elf code
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Fri, 09 Feb 2007 13:35:17 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 09 Feb 2007 05:33:47 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45CC7470.4060002@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <45CC7EC1.76E4.0078.0@xxxxxxxxxx> <45CC7470.4060002@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
But wouldn't that change behavior for domU-s then in an undesirable way? I
would have thought that at best this should be conditional upon __XEN__.

Even better, I would think, would be to split the note namespace to
distinguish
- general required notes
- general optional notes
- dom0 required notes
- etc.

Jan

>>> Gerd Hoffmann <kraxel@xxxxxxx> 09.02.07 14:17 >>>
Jan Beulich wrote:
> Is it intentional that with the new ELF code notes unknown to the hypervisor
> lead to dom0 being unbootable? The old code simply queried for those notes
> mattering at all for dom0, but din't care about any others...

No.

-- 
Gerd Hoffmann <kraxel@xxxxxxx>

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