[Xen-devel] libxl stable API work left (Was: Re: [PATCH 00 of 27 v2] libxl: rationalise libxl_device_* APIs)

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Thu, 2011-10-13 at 10:53 +0100, Ian Campbell wrote:
> Along the way I filed some rough edges of the internal implementation
> of this stuff but my primary concern is to make the public facing API
> one that we can commit to keeping stable.

Speaking of which, my laundry list for things which need to happen to
libxl's API to make it stable contains:
      * The stuff this series addresses
      * Fixup the event API (IanJ)
      * Block script support (IanJ?)
      * The topologyinfo datastructure should be a list of tuples, not a
        tuple of lists.

I've also got:
        I've also been wondering what can/should be done about the split
        between libxl_domain_create_info, libxl_domain_build_info and
        libxl_device_model_info now that they are all bundled together
        in libxl_domain_config and not exposed directly in the API
        (since the related functions became internal, that was before
        4.1). It seems like there ought to be scope for collapsing those
        datastructures somewhat but I'm not sure how yet.
        
But I think this conflicts with the need to do certain bits
asynchronously (primarily for script calling support on create) which I
expect will necessitate splitting libxl_domain_create up again.

If you are (or are going to be) a consumer of the libxl API you would be
well advised to have a read through libxl.h and make sure you are happy
with the rest of it.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel