[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: guest / host buffer sharing ...
From: |
Gerd Hoffmann |
Subject: |
Re: guest / host buffer sharing ... |
Date: |
Wed, 6 Nov 2019 13:50:23 +0100 |
User-agent: |
NeoMutt/20180716 |
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
- guest / host buffer sharing ..., Gerd Hoffmann, 2019/11/05
- Re: guest / host buffer sharing ..., Stefan Hajnoczi, 2019/11/06
- Re: guest / host buffer sharing ...,
Gerd Hoffmann <=
- Re: guest / host buffer sharing ..., Stefan Hajnoczi, 2019/11/07
- Re: guest / host buffer sharing ..., Frank Yang, 2019/11/07
- Re: guest / host buffer sharing ..., Tomasz Figa, 2019/11/20
- Re: guest / host buffer sharing ..., Gerd Hoffmann, 2019/11/08
- Re: guest / host buffer sharing ..., Stefan Hajnoczi, 2019/11/08
- Re: guest / host buffer sharing ..., Stéphane Marchesin, 2019/11/08
- Re: guest / host buffer sharing ..., Stefan Hajnoczi, 2019/11/09
- Re: guest / host buffer sharing ..., Tomasz Figa, 2019/11/09
- Re: guest / host buffer sharing ..., Stefan Hajnoczi, 2019/11/09
- Re: guest / host buffer sharing ..., Tomasz Figa, 2019/11/09