84d6eedd5e
Each driver implemented the Vulkan runtime submit callback itself, which resulted in a lot of duplicated code to iterate through the command buffers and gather the list of IBs to execute, deal with autotune and command buffers with suspending/resuming dynamic renderpasses, etc. This has been getting steadliy worse and was only going to get worse with sparse, since to implement sparse bind submissions we have to similarly traverse and flatten an array of bind structures. Borrow an idea from nvk, and add an abstraction of a "submit" object which holds a (dynamically growing) list of pending commands to submit. We add kernel-specific functions to create a submit, add commands to it, and finally submit it. For sparse, we will add additional an additional function that adds a sparse bind and then we will parse the Vulkan structures in common code. For now, we move various misc. driver-independent parts of the submission path into a common tu_queue_submit() that calls into the new abstractions. In the future, if we need to add driver-internal syncobjs to the user-provided ones, we could use the same approach with waits and signals. For now we provide them as part of the submit function. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/32165>
`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.