docs: Document the implicit barriers around blits
We're going to use resource_copy_region to copy from a resource that has been written to with imageStore. Make it clear that this is safe. Reviewed-by: Tapani Pälli <tapani.palli@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19827>
This commit is contained in:
@@ -665,8 +665,10 @@ Blitting
|
||||
These methods emulate classic blitter controls.
|
||||
|
||||
These methods operate directly on ``pipe_resource`` objects, and stand
|
||||
apart from any 3D state in the context. Blitting functionality may be
|
||||
moved to a separate abstraction at some point in the future.
|
||||
apart from any 3D state in the context. Each method is assumed to have an
|
||||
implicit memory barrier around itself. They do not need any explicit
|
||||
``memory_barrier``. Blitting functionality may be moved to a separate
|
||||
abstraction at some point in the future.
|
||||
|
||||
``resource_copy_region`` blits a region of a resource to a region of another
|
||||
resource, provided that both resources have the same format, or compatible
|
||||
|
Reference in New Issue
Block a user