Re: [PATCH v1 2/4] virtio-msg: Add virtio-msg, a message based virtio transport layer

Hi Demi,

> On 25 Feb 2026, at 13:36, Demi Marie Obenour <[email protected]> wrote:
>
> On 1/26/26 11:32, Bill Mills wrote:
>
> (snip)
>
>> +\msgdef{GET_SHM}
>> +
>> +\msgref{GET_SHM} returns the location and size of a device-owned shared memory
>> +region. The request carries the region index; the response echoes the index and
>> +provides the base address and length. A length of zero indicates that the
>> +specified region does not exist.
>> +
>> +\begin{lstlisting}
>> +struct virtio_msg_get_shm_req {
>> +        le32 index; /* shared memory region index */
>> +};
>> +
>> +struct virtio_msg_get_shm_resp {
>> +        le32 index;  /* echoed index */
>> +        le32 length; /* region length (0 if nonexistent) */
>> +        le32 address;/* region address */
>> +};
>> +\end{lstlisting}
>
> Why only le32?  Some shared memory regions, such as mapped GPU buffers,
> can be much larger than 2^32 bytes.

Very right, i will update this to hold 64bit addresses and length.

Cheers
Bertrand

> --
> Sincerely,
> Demi Marie Obenour (she/her/hers)<OpenPGP_0xB288B55FFF9C22C1.asc>


IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.