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

On Fri, 2011-01-07 at 16:25 +0000, Gianni Tedesco wrote:
> 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

Actually, sorry, that's slightly incorrect. In the final patch
'pyxl-domain-create' the libxl_domain_config struct comes out of libxl.h
and in to the IDL but the net is an identical C program.

That's why arrays and enums are implemented in the IDL.


Xen-devel mailing list

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