mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2025-12-29 05:50:11 +01:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
25b73dff5a
Establish groups of resolve and unresolve operations that the a7xx hardware can then use to improve efficiency. Creating such groups enables continuation of command stream processing while these (un)resolves are in progress, as long as those latter operations don't depend on the grouped (un)resolves. To enable concurrent resolves and unresolves, corresponding fields on the RB_CCU_CNTL register have to be set appropriately. Resolve groups are tracked through a scoped struct that logs any pending resolve operation. Once the group is complete, the emit helper function will write out the CCU_END_RESOLVE_GROUP event to the command stream. The buffer ID field on the RB_BLIT_INFO register can be used to disperse different resolve operations across all available slots in the resolve engine. The 0x8 and 0x9 IDs are reserved for depth and stencil buffers, while the 0x0-0x7 range is used for color buffers. A simple incremented counter is used to assign IDs for all color buffers inside any resolve group. While it can occur for two color or depth/stencil buffers inside the same resolve group to have identical IDs, hardware doesn't seem to have a problem with handling that. Two TU_DEBUG options are provided, 'noconcurrentresolves' and 'noconcurrentunresolves` disable respective operations by adjusting the mode set through RB_CCU_CNTL. Signed-off-by: Zan Dobersek <zdobersek@igalia.com> Reviewed-by: Danylo Piliaiev <dpiliaiev@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/31190> |
||
|---|---|---|
| .ci-farms | ||
| .ci-farms-disabled | ||
| .github/workflows | ||
| .gitlab | ||
| .gitlab-ci | ||
| android | ||
| bin | ||
| build-support | ||
| docs | ||
| include | ||
| src | ||
| subprojects | ||
| .clang-format | ||
| .clang-format-ignore | ||
| .clang-format-include | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .graphqlrc.yml | ||
| .mailmap | ||
| .mr-label-maker.yml | ||
| .shellcheckrc | ||
| CODEOWNERS | ||
| meson.build | ||
| meson_options.txt | ||
| README.rst | ||
| VERSION | ||
`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.