Re: [Xen-devel] future plans for libxl?

[Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>]

On Fri, 16 Apr 2010, Andre Przywara wrote:
> Ian Jackson wrote:
> > Xu, Jiajun writes ("RE: [Xen-devel] future plans for libxl?"):
> >>  And seems following functions are not
> >> supported in 'xl' yet: HAP option, PCI-Passthrough-Strict-Check like
> >> ACS capability check, HVM S3 resume support by 'xm trigger' and
> >> function like 'xm info'.
> > 
> > Thanks for that list.  But yes, we know there are some of the less
> > core features which haven't yet been implemented.  Contributions are
> > welcome!
> I have a working version of xl info ready.

great!

> I have still to think about the best approach for some fields to 
> propagate in libxl_get_version_info and libxl_get_physinfo (bitfields 
> vs. strings). I am not sure what the casual library user would like 
> more: Masking bits or strstr'ing for names? For reporting (as in xl 
> info) compiled strings are easier.
> Any suggestions? (I especially think about xen_caps, virt_caps and 
> xen_scheduler)
> 

feel free to submit your implementation; in general I think masking
bits make a better interface for a library.


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