mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-05-04 20:38:06 +02:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
e96292bc07
Bifrost (and Valhall) separate early-ZS configuration into two fields: when does the depth/stencil buffer update happen? and when are pixels killed by the depth/stencil tests? The driver separately configures these to occur early (before the shader executes) or late (after the ATEST instruction executes at the end of the shader). Early tests are generally more efficient, but various combinations of API state and fragment shader properties can require late updates and/or late kills for correctness. Determining how to configure these fields is nontrivial. Our current implementation (on Bifrost) configures these fields at fragment shader compile time and bakes the settings into the RSD. This is both wrong (using early testing when late testing is required) and suboptimal (using late testing when early testing would suffice). We need to defer this configuration until draw time, when we know rasterizer and Z/S state. Reclassifying at draw time (as we currently do on Valhall) would be expensive, especially with the extra terms added in here. To cope, decouple the shader classification from the draw-time configuration. Since there are only a few bits of draw state involved, this implementation just calculates all possible states. Then the draw time classification is just indexing into a lookup table. The actual algorithm used to classify is written with correctness and clarity in mind. Unlike the current classification algorithm (which tries to match what the DDK does, poorly), this algorithm embeds its proofs of correctness. Signed-off-by: Alyssa Rosenzweig <alyssa@collabora.com> Cc: mesa-stable Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17428> |
||
|---|---|---|
| .github/workflows | ||
| .gitlab/issue_templates | ||
| .gitlab-ci | ||
| android | ||
| bin | ||
| build-support | ||
| docs | ||
| include | ||
| src | ||
| subprojects | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| 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://mesa3d.org/install.html>`_), but the recommended way is to use Meson (`docs/meson.rst <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 `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://mesa3d.org/bugs.html>`_). Contributing ------------ Contributions are welcome, and step-by-step instructions can be found in our documentation (`docs/submittingpatches.rst <https://mesa3d.org/submittingpatches.html>`_). Note that Mesa uses gitlab for patches submission, review and discussions.