mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-01-04 20:00:11 +01:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
e3cb620b55
In a hybrid graphics setup, Mesa allocates two buffers for the window surface. The first is what the discrete card renders to; it lives in VRAM and is usually tiled and possibly compressed. The second is a shadow copy that lives in system memory (readable by the integrated card with the displays); it's usually linear and uncompressed. Mesa's window system code schedules blits to update the shadow copy when needed, typically at the end of a frame. These can be fairly costly when running a full-screen application at high resolutions. We'd like to use the blitter for these copies, as it lets us perform the copy asynchronously, letting the 3D engine race ahead and start rendering the next frame. If we used the 3D engine, the next frame could not start rendering until the PRIME blit finishes, giving us less time to draw the frame. Fortunately, Tigerlake introduced new blitter commands which can operate at full memory bandwidth. DRI PRIME blits happen via the Gallium blit() hook. We can detect that case by looking for the PIPE_BIND_PRIME_BLIT_DST flag on the destination resource. This patch detects that case and calls iris_copy_region() on IRIS_BATCH_BLITTER to handle it. We know a priori that the blitter can handle this operation (it's not a scaled blit, the formats match and should not be 96bpp, there's no combined depth stencil, or other weird edge cases). blorp_copy() will also assert that edge cases don't occur. Together with the next patch, this improves performance on DG1 Hybrid scenarios by about 5-6%. Reviewed-by: Nanley Chery <nanley.g.chery@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13877> |
||
|---|---|---|
| .gitlab/issue_templates | ||
| .gitlab-ci | ||
| android | ||
| bin | ||
| build-support | ||
| docs | ||
| include | ||
| src | ||
| subprojects | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .travis.yml | ||
| 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.