[Mesa-dev] Merging virtio-gpu vulkan driver
airlied at gmail.com
Mon Apr 5 18:12:37 UTC 2021
On Tue, 6 Apr 2021 at 03:22, Chia-I Wu <olvaffe at gmail.com> wrote:
> Hi list,
> We are looking to merge virtio-gpu vulkan driver
> On the good side, the driver is conformant with Vulkan 1.2 (vtest) and
> Vulkan 1.1 (virtio-gpu). I only tried it on a handful of games (e.g.,
> Dota 2, Hades on Proton with D3D and Vulkan backends, and some
> others), but it appeared to work with reasonable framerates. I was
> told that it works with other games as well.
> I tried Basemark GPU a month ago on a Core i7-7820HQ. The fps numbers were
> quality highend: native 17.07, vtest 16.83, virtio-gpu 16.65
> quality medium: native 98.19, vtest 91.15, virtio-gpu 92.29
> quality simple: native 327.52, vtest 317.17, virtio-gpu 283.02
> On the bad side, the driver requires
> VIRTIO_GPU_F_RESOURCE_BLOB (kernel 5.11 but not supported by qemu)
> VIRTIO_GPU_F_CONTEXT_INIT (to be upstreamed)
> As a result, it can only be tested with crosvm or vtest.
I've no major objections to merging this in an experimental state, not
having qemu support is of course an annoyance but at some point I
suppose that bridge will have to be crossed.
My main worry with no qemu support is locking in crosvm specific
behaviours that we later can't get back out of.
> We develop using anv as the host driver mostly. Simple samples work
> when the host driver is radv, but games hit a host KVM bug quickly.
> The issue has been reported and we expect it to be fixed by upstream.
> The protocol for Vulkan command serialization is not finalized either.
> The driver is still marked experimental and must be enabled with
> -Dvulkan-drivers=virtio-experimental. The plan is to mark the driver
> stable after the kernel ABI and the protocol ABI are finalized.
Is the virglrenderer side merged? or is it a case of both sides
landing close to each other.
>  https://gitlab.freedesktop.org/virgl/drm-misc-next/-/commits/context-init/
>  KVM-based VMM written in Rust
>  vtest is a part of virglrenderer and is what I use for most of the
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
More information about the mesa-dev