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/
Home Products Support Community News


Re: [Xen-devel] [PATCH 0 of 4] Python libxl binding updates

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0 of 4] Python libxl binding updates
From: Gianni Tedesco <gianni.tedesco@xxxxxxxxxx>
Date: Fri, 7 Jan 2011 16:25:33 +0000
Cc: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Delivery-date: Fri, 07 Jan 2011 08:26:07 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <patchbomb.1291902839@xxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <patchbomb.1291902839@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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

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

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.



Xen-devel mailing list

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