So, we could create a block-general lifetime ioctl with many reserved bytes, or create a virtio block specific ioctl without reserved bytes at all. I think that we should keep it virtio specific, and if a new lifetime command is added to the spec with more fields, we could create a new ioctl. Does Everyone agree? > I think if you are going to pass struct virtio_blk_lifetime to > userspace, better pass it as defined in the spec, in LE format. > It's unusual for an ioctl to produce a struct that's not in CPU > endianness. I think the kernel should deal with endianness here. I'm not sure how to proceed with the endianness matter.. Alvaro _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
