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

[Xen-devel] [PATCH RFC 0/9] libxl error reporting



Following the proposal from Euan Harris to improve libxl's error reporting [1],
I have written a first couple of patches that I would like some feedback on.
The focus of these patches is on improving the errors that can be raised by the
device_add functions and some related ones.

Does the approach look acceptable?
Do the error codes make sense?
Did I miss any error conditions?

One thing I wasn't sure about is what happens if libxl__wait_device_connection
times out.

Also, I realise that these patches essentially break backward compatibility,
and I have not done the "#define LIBXL_HAVE" stuff yet. Do people consider this
necessary, and if so, at what granularity (e.g. one LIBXL_HAVE for all new
error codes in a release)?

Thanks,
Rob

[1] http://lists.xen.org/archives/html/xen-devel/2015-05/msg02572.html

_______________________________________________
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®.