(resending this one with Julien's right address.)
Ian Jackson writes ("Re: [PATCH 1/3] docs: specify endianess of xenstore
protocol header"):
> Juergen Gross writes ("[PATCH 1/3] docs: specify endianess of xenstore
> protocol header"):
> > The endianess of the xenstore protocol header should be specified.
> ...
> > -followed by xsd_sockmsg.len bytes of payload.
> > +followed by xsd_sockmsg.len bytes of payload. The header fields are
> > +all in little endian byte order.
>
> Yes, but this is not correct. On a big-endian cpu, they would be in
> big-endian.
>
> On a bytesexual cpu, the endianness should be specified but it will be
> the same endianness as shared ring fields, etc. So this doc probably
> ought not to contain a list of endiannesses. Best just to say that
> the fields are all in host native byte order.
Also: in the subject, `endianess' should be `endianness'.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
