> Am 03.08.2020 um 22:59 schrieb Michael S. Tsirkin <mst@xxxxxxxxxx>: > > Since this is a modern-only device, > tag config space fields as having little endian-ness. > > TODO: check other uses of __virtioXX types in this header, > should probably be __leXX. Doesn‘t matter in practice IIRC, like this change. But we could do it (the spec documents everything as __le) in case it makes things clearer. Acked-by: David Hildenbrand <david@xxxxxxxxxx> > > Signed-off-by: Michael S. Tsirkin <mst@xxxxxxxxxx> > --- > include/uapi/linux/virtio_mem.h | 14 +++++++------- > 1 file changed, 7 insertions(+), 7 deletions(-) > > diff --git a/include/uapi/linux/virtio_mem.h b/include/uapi/linux/virtio_mem.h > index a9ffe041843c..70e01c687d5e 100644 > --- a/include/uapi/linux/virtio_mem.h > +++ b/include/uapi/linux/virtio_mem.h > @@ -185,27 +185,27 @@ struct virtio_mem_resp { > > struct virtio_mem_config { > /* Block size and alignment. Cannot change. */ > - __u64 block_size; > + __le64 block_size; > /* Valid with VIRTIO_MEM_F_ACPI_PXM. Cannot change. */ > - __u16 node_id; > + __le16 node_id; > __u8 padding[6]; > /* Start address of the memory region. Cannot change. */ > - __u64 addr; > + __le64 addr; > /* Region size (maximum). Cannot change. */ > - __u64 region_size; > + __le64 region_size; > /* > * Currently usable region size. Can grow up to region_size. Can > * shrink due to VIRTIO_MEM_REQ_UNPLUG_ALL (in which case no config > * update will be sent). > */ > - __u64 usable_region_size; > + __le64 usable_region_size; > /* > * Currently used size. Changes due to plug/unplug requests, but no > * config updates will be sent. > */ > - __u64 plugged_size; > + __le64 plugged_size; > /* Requested size. New plug requests cannot exceed it. Can change. */ > - __u64 requested_size; > + __le64 requested_size; > }; > > #endif /* _LINUX_VIRTIO_MEM_H */ > -- > MST > _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization