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] [PATCH 0 of 5] XCP: Allow XCP to use ocaml library bindi

To: Vincent Hanquez <Vincent.Hanquez@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0 of 5] XCP: Allow XCP to use ocaml library bindings in Xen unstable (which will become Xen 4.1) -- xen-unstable.hg
From: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Date: Thu, 16 Dec 2010 09:56:19 +0000
Cc: "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Thu, 16 Dec 2010 02:06:05 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D08A092.4020103@xxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Citrix Systems, Inc.
References: <1291732233.13966.3198.camel@xxxxxxxxxxxxxxxxxxxxxx> <patchbomb.1291732371@xxxxxxxxxxxxxxxxxxxxxx> <alpine.DEB.2.00.1012131723340.2390@kaball-desktop> <4D08A092.4020103@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2010-12-15 at 11:03 +0000, Vincent Hanquez wrote:
> On 13/12/10 17:23, Stefano Stabellini wrote:
> > Vincent, do you have any comments on these?
> 
> Not much. Personally I think it would be better that xcext is folded in 
> xc. It just make the moving to upstream module more transparent, and the
> convergence quicker.

> It's also probably required that libxl knows to use stuff that have been 
> left in xcext if XCP/XCI is ever going to use it.

The stuff in xcext depends on features/interfaces which are only in the
XCP hypervisor patch queue and not upstream which is why I didn't add
the support upstream libxc.

When those hypervisor patches get upstreamed then the bindings should be
added to upstream libxc (or possibly libxl in some cases) at that time.
Certainly the intention should be that xcext disappears with time.

In the meantime perhaps it would make sense to add patches to the XCP
patch queue to add those features to libxc there instead of having
xcext.

I think some of xcext might also be obsolete and doesn't do anything on
modern hypervisors but I didn't check that closely.

Ian.


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

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