[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v5 04/17] libxc/libxl: sanitize error handling in *_get_max_{cpus, nodes}



Dario Faggioli writes ("[PATCH v5 04/17] libxc/libxl: sanitize error handling 
in *_get_max_{cpus, nodes}"):
> In libxc, make xc_get_max_{cpus,node}() always return either a
> positive number or -1, and change all the callers to deal with
> that.
> 
> In libxl, make libxl_get_max_{cpus,nodes}() always return either a
> positive number or a libxl error code. Thanks to that, it is also
> possible to fix loggig for libxl_{cpu,node}_bitmap_alloc(), which
> now happens inside the functions themselves, more accurately
> reporting what happened.
> 
> Note that libxl_{cpu,node}_bitmap_alloc() are also moved to
> libxl_utils.c as, apart from having become less trivial and hence
> better suited there, that's required for using GC_INIT()/GC_FREE,
> which in turn is needed for the LOG()/LOGE() macros.
> 
> Signed-off-by: Dario Faggioli <dario.faggioli@xxxxxxxxxx>
> Acked-by: George Dunlap <george.dunlap@xxxxxxxxxxxxx>

Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.