> > You don't have to use the rendering pipeline. You can let the i915 gpu > > render into a dma-buf shared with virtio-gpu, then use virtio-gpu only for > > buffer sharing with the host. > [Kasireddy, Vivek] Is this the most viable path forward? I am not sure how complex or > feasible it would be but I'll look into it. > Also, not using the rendering capabilities of virtio-gpu and turning it into a sharing only > device means there would be a giant mode switch with a lot of if() conditions sprinkled > across. Are you OK with that? Hmm, why a big mode switch? You should be able to do that without modifying the virtio-gpu guest driver. On the host side qemu needs some work to support the most recent virtio-gpu features like the buffer uuids (assuming you use qemu userspace), right now those are only supported by crosvm. It might be useful to add support for display-less virtio-gpu, i.e. "qemu -device virtio-gpu-pci,max_outputs=0". Right now the linux driver throws an error in case no output (crtc) is present. Should be fixable without too much effort though, effectively the sanity check would have to be moved from driver initialization to commands like SET_SCANOUT which manage the outputs. take care, Gerd _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
