On Fri, Oct 06, 2017 at 08:00:00PM +0100, Andrew Cooper wrote: > Mixed throughout libxc are uint32_t, int, and domid_t for domid parameters. > With a signed type, and an explicitly 16-bit type, it is exceedingly difficult > to construct an INVALID_DOMID constant which works with all of them. (The > main problem being that domid_t gets unconditionally zero extended when > promoted to int for arithmatic.) > > Libxl uses uint32_t consistently everywhere, so alter libxc to match.
I would rather using domid_t throughout in libxc. Is there any problem with that? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
