Find a file
Karol Herbst 9d7441dcb0 gallium: add fixed address resource API
cl_ext_buffer_device_address requires us to set a fixed address for a
given memory allocation. As this extension is intended to be implemented
on top of vulkan we have to take its limitations into account.

For SVM we'll add proper VM management interfaces, but zink won't be able
to implement those, so here we are.

The old interfaces added back in clover's time were modeled after a very
bindful resource model and the frontend was require to bind all the used
resources ahead of launch_grid.

cl_ext_buffer_device_address and also SVM however will require us to
dynamically attach a list of buffers used in a dispatch with known
addresses, hence set_global_binding isn't really suited for those use
cases.

So PIPE_RESOURCE_FLAG_FIXED_ADDRESS is added to tell a driver that the
address of a resource needs to stay the same over its lifetime, which then
can be queried via pipe_screen::resource_get_address.

All such buffers then can be either bound via set_global_binding or passed
in via pipe_grid_info::globals.

Reviewed-by: Adam Jackson <ajax@redhat.com>
Reviewed-by: Alyssa Rosenzweig <alyssa@rosenzweig.io>
Reviewed-by: Marek Olšák <marek.olsak@amd.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/32942>
2025-05-28 19:21:46 +00:00
.ci-farms ci: Disable fd-farm 2025-05-23 15:27:16 +00:00
.ci-farms-disabled ci/bare-metal: Remove remnants of old bare-metal setups 2025-05-26 10:19:29 +00:00
.github/workflows
.gitlab
.gitlab-ci ci: Don't forward long environment variables 2025-05-28 18:44:16 +00:00
.marge/hooks
android android: fix llvmpipe build rules 2025-05-23 08:58:03 +02:00
bin ci: Remove debian/x86_64_pyutils container 2025-05-26 17:25:40 +00:00
build-support
docs gallium: add fixed address resource API 2025-05-28 19:21:46 +00:00
include include: sync CL headers 2025-05-28 19:21:46 +00:00
licenses
src gallium: add fixed address resource API 2025-05-28 19:21:46 +00:00
subprojects meson: add wrap for libdrm 2025-05-27 16:07:29 +00:00
.clang-format
.clang-format-ignore
.clang-format-include
.dir-locals.el
.editorconfig
.git-blame-ignore-revs
.gitattributes
.gitignore
.gitlab-ci.yml ci: Remove debian/x86_64_pyutils container 2025-05-26 17:25:40 +00:00
.graphqlrc.yml
.mailmap mailmap: update my name and email 2025-05-07 00:26:45 +00:00
.mr-label-maker.yml mr-label-maker.yml: Add mediafoundation tag and associated directories 2025-05-23 15:30:04 +00:00
.shellcheckrc
CODEOWNERS
meson.build meson: add wrap for libdrm 2025-05-27 16:07:29 +00:00
meson.options meson: add wrap for libdrm 2025-05-27 16:07:29 +00:00
README.rst
rustfmt.toml
VERSION VERSION: bump to 25.2 2025-04-16 14:30:14 +02:00

`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.