Gurchetan Singh
a5788932c9
This uses libvirtgpu_kumquat_ffi.so to send commands to the Kumquat Media Server. The implementation of Kumquat is found at crrev.com/c/5645904. This is a more complex, but more fully featured end-to-end testing framework. This biggest benefit it is can run complex apps (vkcube, gfxbench + ANGLE/Zink) on Linux, without a VM or a full Android tree. The rutabaga FFI path -- which relied on a nested Vulkan loader -- didn't work for complex apps and funkiness was observed with the nested Vulkan loader. Plus, app 1 + app 2 could connect Kumquat at the same time. This may also benefit snapshot tests, particular since end to end flow relies on external blob. For example, a snapshot save command could actually call stream_renderer_teardown(..) on the host-side, while the guest retains it's state (ASG mappings + vulkano mappings). A snapshot restore would actually call stream_renderer_init(..) + stream_renderer_restore(..), which an actual upstream VMM would do. Another additional benefit is multi-context testing. Since libvirtgpu_kumquat_ffi.so is portable, other libraries (minigbm) can also call it. We can mimic the cross-domain context allocating via libminigbm.so, while context libgfxstream_vulkan.so imports the file descriptor. This change only transitions the meson build since the main goal is once again is Linux on Linux testing w/o an Android tree. Reviewed-by: Aaron Ruby <aruby@blackberry.com> Acked-by: Yonggang Luo <luoyonggang@gmail.com> Acked-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27246>
`Mesa <https://mesa3d.org>`_ - The 3D Graphics Library ====================================================== Source ------ This repository lives at https://gitlab.freedesktop.org/mesa/mesa. Other repositories are likely forks, and code found there is not supported. Build & install --------------- You can find more information in our documentation (`docs/install.rst <https://docs.mesa3d.org/install.html>`_), but the recommended way is to use Meson (`docs/meson.rst <https://docs.mesa3d.org/meson.html>`_): .. code-block:: sh $ meson setup build $ ninja -C build/ $ sudo ninja -C build/ install Support ------- Many Mesa devs hang on IRC; if you're not sure which channel is appropriate, you should ask your question on `OFTC's #dri-devel <irc://irc.oftc.net/dri-devel>`_, someone will redirect you if necessary. Remember that not everyone is in the same timezone as you, so it might take a while before someone qualified sees your question. To figure out who you're talking to, or which nick to ping for your question, check out `Who's Who on IRC <https://dri.freedesktop.org/wiki/WhosWho/>`_. The next best option is to ask your question in an email to the mailing lists: `mesa-dev\@lists.freedesktop.org <https://lists.freedesktop.org/mailman/listinfo/mesa-dev>`_ Bug reports ----------- If you think something isn't working properly, please file a bug report (`docs/bugs.rst <https://docs.mesa3d.org/bugs.html>`_). Contributing ------------ Contributions are welcome, and step-by-step instructions can be found in our documentation (`docs/submittingpatches.rst <https://docs.mesa3d.org/submittingpatches.html>`_). Note that Mesa uses gitlab for patches submission, review and discussions.