On Thu, Jul 29, 2021 at 03:52:46PM +0200, Vitaly Kuznetsov wrote:
> Siddharth Chandrasekaran <sidcha@xxxxxxxxx> writes:
>
> > According to Hyper-V TLFS Version 6.0b, struct hv_message_header members
> > should be defined in the order:
> >
> > message_type, reserved, message_flags, payload_size
> >
> > but we have it defined in the order:
> >
> > message_type, payload_size, message_flags, reserved
> >
> > that is, the payload_size and reserved members swapped.
>
> Indeed,
>
> typedef struct
> {
> HV_MESSAGE_TYPE MessageType;
> UINT16 Reserved;
> HV_MESSAGE_FLAGS MessageFlags;
> UINT8 PayloadSize;
> union
> {
> UINT64 OriginationId;
> HV_PARTITION_ID Sender;
> HV_PORT_ID Port;
> };
> } HV_MESSAGE_HEADER;
Well. I think TLFS is wrong. Let me ask around.
Wei.
