0c05d46237
Even though we normally use the CP_BLIT path with resolves that aren't aligned, there's a special case when we're resolving the entire image and there's enough padding so that we can still use CP_EVENT_WRITE::BLIT when the render area isn't aligned. The hardware seems to not like unaligned scissors when not clearing, and sometimes hangs rather than silently round the scissor. This causes hangs in e.g. dEQP-VK.glsl.derivate.dfdx.texture.msaa4.float_highp. There was some concern that the CP_BLIT path might use this scissor also, but I confirmed that this isn't the case by setting it to 0 before resolving and then noting that CP_BLIT still works (but CP_EVENT_WRITE doesn't). Furthermore, this is actually impossible because of how the 2D engine is set up: it gets its own pair of register banks, which can be switched independently of the 3D register banks, so that 2D events (CP_BLIT) normally aren't synchronized relative to 3D events (CP_EVENT_WRITE, CP_DRAW_*, and CP_EXEC_CS) and therefore they can't share any registers except for non-pipelined registers like RB_CCU_CNTL that don't use the register bank mechanism at all. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4585> |
||
---|---|---|
.appveyor | ||
.gitlab/issue_templates | ||
.gitlab-ci | ||
bin | ||
build-support | ||
docs | ||
doxygen | ||
include | ||
scons | ||
src | ||
subprojects | ||
.dir-locals.el | ||
.editorconfig | ||
.gitignore | ||
.gitlab-ci.yml | ||
.mailmap | ||
.travis.yml | ||
Android.common.mk | ||
Android.mk | ||
CleanSpec.mk | ||
README.rst | ||
REVIEWERS | ||
SConstruct | ||
VERSION | ||
appveyor.yml | ||
common.py | ||
meson.build | ||
meson_options.txt |
README.rst
`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.html <https://mesa3d.org/install.html>`_), but the recommended way is to use Meson (`docs/meson.html <https://mesa3d.org/meson.html>`_): .. code-block:: sh $ mkdir build $ cd build $ meson .. $ sudo ninja install Support ------- Many Mesa devs hang on IRC; if you're not sure which channel is appropriate, you should ask your question on `Freenode's #dri-devel <irc://chat.freenode.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.html <https://mesa3d.org/bugs.html>`_). Contributing ------------ Contributions are welcome, and step-by-step instructions can be found in our documentation (`docs/submittingpatches.html <https://mesa3d.org/submittingpatches.html>`_). Note that Mesa uses gitlab for patches submission, review and discussions.