Why does Qemu need a new Wayland UI backend? The main reason why there needs to be a plain and simple Wayland backend for Qemu UI is to eliminate the Blit (aka GPU copy) that happens if using a toolkit like GTK or SDL (because they use EGL). The Blit can be eliminated by sharing the dmabuf fd -- associated with the Guest scanout buffer -- directly with the Host compositor via the linux-dmabuf (unstable) protocol. Once properly integrated, it would be potentially possible to have the scanout buffer created by the Guest compositor be placed directly on a hardware plane on the Host thereby improving performance. Only Guest compositors that use multiple back buffers (at-least 1 front and 1 back) and virtio-gpu would benefit from this work.
v2: - Add support for handling/forwarding keyboard and mouse events. - Augment handling of events to ensure that they are not lost in a multi-threaded environment. - Rebase Cc: Gerd Hoffmann <kra...@redhat.com> Cc: Marc-André Lureau <marcandre.lur...@redhat.com> Cc: Dongwon Kim <dongwon....@intel.com> Cc: Tina Zhang <tina.zh...@intel.com> Cc: Satyeshwar Singh <satyeshwar.si...@intel.com> Vivek Kasireddy (2): virtio-gpu: Add support for VIRTIO_GPU_F_RELEASE_FENCE ui: Add a plain Wayland backend for Qemu UI configure | 8 +- hw/display/virtio-gpu-base.c | 3 + hw/display/virtio-gpu-udmabuf.c | 4 +- hw/display/virtio-gpu.c | 54 +- include/hw/virtio/virtio-gpu.h | 6 + include/standard-headers/linux/virtio_gpu.h | 2 + meson.build | 33 + meson_options.txt | 2 + qapi/ui.json | 3 + ui/meson.build | 52 ++ ui/wayland.c | 628 ++++++++++++++++++++ 11 files changed, 791 insertions(+), 4 deletions(-) create mode 100644 ui/wayland.c -- 2.30.2