From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH 0 of 5] XCP: Allow XCP to use ocaml library bindings in Xen unstable (which will become Xen 4.1) -- xen-unstable.hg Date: Thu, 16 Dec 2010 09:56:19 +0000 Message-ID: <1292493379.32368.7035.camel@zakaz.uk.xensource.com> References: <1291732233.13966.3198.camel@zakaz.uk.xensource.com> <4D08A092.4020103@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4D08A092.4020103@eu.citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Vincent Hanquez Cc: "xen-api@lists.xensource.com" , "xen-devel@lists.xensource.com" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org 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.