Ian Campbell writes ("Re: [Xen-devel] [PATCH 2/2] libxl: fix UUID usage on
FreeBSD"):
> On Fri, 2016-01-15 at 16:11 +0100, Roger Pau Monné wrote:
> > Yes, we can remove the uuid_t from libxl_uuid, but this is AFAICT a
> > structure that belongs to the stable API.
>
> Oh b*m, so it is.
I think we may have to bite this bullet. Perhaps we could make an
#ifdef that softened the blow on systems with sane uuid_t.
Given that we have discovered that uuid_t is sometimes insane, I think
we really really want to avoid it.
> Or can we get rid of uuid_raw (which is not touched, and is less likely to
> be given that it is only on a subset of platforms) and have libxl
> _internal_ stuff convert to a byte array.
We don't want to do any byteswapping. That way lies utter madness.
At the libxl API/ABI uuids should be represented as sequences of 16
octets in network byte order (BE).
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
