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

[Xen-devel] bimodal backend operation

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] bimodal backend operation
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Tue, 09 Jan 2007 11:11:21 +0000
Delivery-date: Tue, 09 Jan 2007 03:09:33 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Now that the 32on64 patches have mostly been merged, what is the plan wrt
making the non-compatible backends bimodal capable? While Gerd's suggested
approach is clearly less involved than mine, I continue to dislike the idea of
having to touch the frontends so that those can inform the backend about
their protocol version; I had hoped that this can be done fully backward
compatibly (except perhaps for pv drivers in hcm guests) by allowing the
backend to learn the address size of the guest, which the tools can know
pretty early during domain creation.

Thanks, Jan

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

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