Hi,
> In the graphics buffer sharing use case, how does the other side
> determine how to interpret this data?
The idea is to have free form properties (name=value, with value being
a string) for that kind of metadata.
> Shouldn't there be a VIRTIO
> device spec for the messaging so compatible implementations can be
> written by others?
Adding a list of common properties to the spec certainly makes sense,
so everybody uses the same names. Adding struct-ed properties for
common use cases might be useful too.
cheers,
Gerd
