[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.