From: Gianni Tedesco Subject: Re: [PATCH 0 of 4] Python libxl binding updates Date: Fri, 7 Jan 2011 16:25:33 +0000 Message-ID: <1294417533.12018.71.camel@qabil.uk.xensource.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "xen-devel@lists.xensource.com" Cc: Ian Campbell , Ian Jackson List-Id: xen-devel@lists.xenproject.org On Thu, 2010-12-09 at 13:53 +0000, Gianni Tedesco wrote: > Various, mostly minor, updates to the libxl python binding which address both > correctness and usability issues. I have a new version of this patch-set which currently contains 10 patches and brings the bindings up to a state where we can create domains and all that is left is basic plumbing through of libxl functions/methods. Do you think it would be possible to get a freeze exception so that I can re-submit this next week? It provides new features but only to the xl python bindings which are unused and unusable in their current state anyway. There are bugfixes: 1. pyxl-fix-refcounting 2. pyxl-unmuddle-pause-unpause Some IDL and code-generation work which touches things in the tools/libxl tree but doesn't change any C code (not even the auto-generated headers and destructors). I have decided not to abolish keyed unions after all. 1. pyxl-marshall-substructures-and-unions 2. xl-idl-arrays 3. xl-idl-enums 4. pyxl-builtin-type-marshallers Exporting more things: 1. pyxl-add-int-constants 2. pyxl-allow-subclassing 3. pyxl-pci-passthrough 4. pyxl-domain-create The last of which depends on my previous patch to re-work domain creation in libxl. Thanks Gianni