mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-01-27 16:20:24 +01:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
26364c6347
When a batch fails we either recreate our context (in case we got -EIO or -ENOMEM) or we abort() (every other error). If we don't abort and a later batch has a dependency on the batch that failed, then this newer batch will fail with -EINVAL since it requires a syncobj that was never submitted, which means we'll abort(). To avoid this problem, in this patch we simply signal syncobjs of failed batches. This means we may be breaking our dependency tracking, but IMHO it's better than simply letting it abort() later. In other words, this moves the situation for some apps from "app causes a GPU hang and then aborts" to "app causes a GPU hang but keeps running". Note: on some older Kernels (like today's Debian 5.10 Kernel) I see X simply freezing after the GPU hang when the app doesn't decide to abort(). Switching to a more recent Kernel fixes this issue for me, so in case it happens to you make sure you have the most recent stable trees. v2: - Fix coding style (Ken). - Use the big comment block provided by Ken (Ken). - Adjust the commit message so avoid saying we retry (Ken). - Rebase after the syncobj ownership changes. - Drive-by add a missing white space in the header. Acked-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com> Reviewed-by: Kenneth Graunke <kenneth@whitecape.org> Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12657> |
||
|---|---|---|
| .gitlab/issue_templates | ||
| .gitlab-ci | ||
| android | ||
| bin | ||
| build-support | ||
| docs | ||
| include | ||
| src | ||
| subprojects | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .travis.yml | ||
| meson.build | ||
| meson_options.txt | ||
| README.rst | ||
| REVIEWERS | ||
| 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.