mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-03-15 10:40:39 +01:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
85394f39e5
In some situations we can have multiple present queued with the same target_msc and in this case we might get the last one signaled before the previous ones. Here's an example with some debug logs added to the relevant functions: loader_dri3_swap_buffers_msc: new send_sbc=2323 - target_msc=337 dri3_handle_present_event: old recv_sbc=2322 msc=338 new_recv_sbc=2323 loader_dri3_swap_buffers_msc: new send_sbc=2324 - target_msc=338 dri3_handle_present_event: old recv_sbc=2323 msc=338 new_recv_sbc=2324 loader_dri3_swap_buffers_msc: new send_sbc=2325 - target_msc=338 dri3_handle_present_event: old recv_sbc=2324 msc=338 new_recv_sbc=2325 loader_dri3_swap_buffers_msc: new send_sbc=2326 - target_msc=338 loader_dri3_swap_buffers_msc: new send_sbc=2327 - target_msc=338 loader_dri3_swap_buffers_msc: new send_sbc=2328 - target_msc=338 dri3_handle_present_event: old recv_sbc=2325 msc=338 new_recv_sbc=2327 loader_dri3_swap_buffers_msc: new send_sbc=2329 - target_msc=338 dri3_handle_present_event: old recv_sbc=2327 msc=338 new_recv_sbc=2328 loader_dri3_swap_buffers_msc: new send_sbc=2330 - target_msc=338 dri3_handle_present_event: old recv_sbc=2328 msc=338 new_recv_sbc=2329 loader_dri3_swap_buffers_msc: new send_sbc=2331 - target_msc=338 dri3_handle_present_event: old recv_sbc=2329 msc=338 new_recv_sbc=2330 dri3_handle_present_event: old recv_sbc=2330 msc=338 new_recv_sbc=2326 # oops dri3_handle_present_event: old recv_sbc=2326 msc=339 new_recv_sbc=2331 It's usually harmless, except if Mesa ends up using loader_dri3_swapbuffer_barrier right after the out-of-order event. In this example it's ok because more swaps are executed after 2330, so waiting for read_sbc>=2330 would work anyway. But if this wasn't the case, loader_dri3_swapbuffer_barrier would never return, waiting for recv_sbc to become >= 2330 while it's stuck at 2326 because the later swaps were processed earlier. Reviewed-by: Marek Olšák <marek.olsak@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/39857> |
||
|---|---|---|
| .ci-farms | ||
| .ci-farms-disabled | ||
| .github/workflows | ||
| .gitlab | ||
| .gitlab-ci | ||
| .marge/hooks | ||
| android | ||
| bin | ||
| build-support | ||
| docs | ||
| include | ||
| licenses | ||
| 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 | ||
| clippy.toml | ||
| CODEOWNERS | ||
| meson.build | ||
| meson.options | ||
| README.rst | ||
| rustfmt.toml | ||
| 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.