[virglrenderer-devel] multiprocess model and GL

[Gerd Hoffmann]

  Hi,

> Yup, all these use cases need something like the proposed
> VIRTIO_GPU_CMD_RESOURCE_CREATE_V2:
> 
> https://gitlab.freedesktop.org/virgl/drm-misc-next/commit/6a940ed44df9cf8b5180d41571075c498208c81b#b3445381d2f5e962a33780262c87a47085b70f27_254_283
> 
> Check out the userspace here:
> 
> https://gitlab.freedesktop.org/virgl/virglrenderer/merge_requests/303/diffs?commit_id=31b36c7941db74f3b2d38a9af6fa424ee1983c55
> 
> It's pretty much like INIT_BLOB, but it's versioned by the host
> enderer capabilities and can attach iovecs, can create guest dma-bufs
> etc. based on flags.
> 
> We can limit args_size to something reasonable (say 64 bytes).  We can
> also say args_size == 0  is fine for dumb backends (though, without
> metadata query, dumb_create should suffice?) and creates the
> res_id->struct mapping for 3D backends.  kraxel, wdyt?

I think the allocate-via-execbuffer approach is better than using flags
and args[] in VIRTIO_GPU_CMD_RESOURCE_CREATE_V2 ...

cheers,
  Gerd