Anthony Liguori <aligu...@us.ibm.com> writes:
> "Michael S. Tsirkin" <m...@redhat.com> writes:
>> + case offsetof(struct virtio_pci_common_cfg, device_feature_select):
>> + return proxy->device_feature_select;
>
> Oh dear no... Please use defines like the rest of QEMU.
It is pretty ugly.
Yet the structure definitions are descriptive, capturing layout, size
and endianness in natural a format readable by any C programmer.
So AFAICT the question is, do we put the required
#define VIRTIO_PCI_CFG_FEATURE_SEL \
(offsetof(struct virtio_pci_common_cfg, device_feature_select))
etc. in the kernel headers or qemu?
> Haven't looked at the proposed new ring layout yet.
No change, but there's an open question on whether we should nail it to
little endian (or define the endian by the transport).
Of course, I can't rule out that the 1.0 standard *may* decide to frob
the ring layout somehow, but I'd think it would require a compelling
reason. I suggest that's 2.0 material...
Cheers,
Rusty.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
