Hi
On Tue, Jun 19, 2018 at 8:54 AM, Gerd Hoffmann wrote:
> Hi,
>
>> +VHOST_USER_GPU_SCANOUT,
>> +VHOST_USER_GPU_UPDATE,
>> +VHOST_USER_GPU_DMABUF_SCANOUT,
>> +VHOST_USER_GPU_DMABUF_UPDATE,
>
> Hmm, still two command versions.
>
> I still think there should be no separate 2d code
Hi,
> +VHOST_USER_GPU_SCANOUT,
> +VHOST_USER_GPU_UPDATE,
> +VHOST_USER_GPU_DMABUF_SCANOUT,
> +VHOST_USER_GPU_DMABUF_UPDATE,
Hmm, still two command versions.
I still think there should be no separate 2d code path. Just
put the 2d display updates into a texture, or into a drm bu
Add new virtio-gpu devices with a "vhost-user" property. Tthe
associated vhost-user backend is used to handle the virtio rings and
provide rendering results thanks to the vhost-user-gpu protocol.
Example usage:
-object vhost-user-backend,id=vug,cmd="./vhost-user-gpu"
-device vhost-user-vga,vhost-u
