Re: [Xen-devel] [PATCH v4 03/11] public: xen.h: add definitions for UUID handling

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 23.08.17 at 13:08, <volodymyr_babchuk@xxxxxxxx> wrote:
> On 23.08.17 11:10, Jan Beulich wrote:
>>>>> On 22.08.17 at 16:37, <volodymyr_babchuk@xxxxxxxx> wrote:
>>> I can't see why you want to map UUID to a certain structure.
>> 
>> This is so that the type cannot mistakenly be passed to a function
>> taking unsigned char *, or be assigned to a variable of that type.
> Right, I see the point there.
> 
>> Please see our TYPE_SAFE() macro which we use to specifically
>> enclose certain scalar types in a structure to that they won't be
>> compatible with other types deriving from the same scalar base type.
> I see. So what about
> 
> struct xen_uuid_t
> {
>       uint8_t a[16];
> };
> 
> then?

Yes, that's what I had asked for as the minimal solution. That
would be in line with (but better than) xen_domain_handle_t,
which I've just realized we also have.

> One can convert it to union with different representations (array, 
> RFC4122 struct, etc) later if there will be need for this.

Well, why don't you make it a union but stick to just the array
for now if you dislike making it similar to the EFI one? That way
we can add further representations if needed/desired without
breaking existing consumers.

Jan


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