From 0a5a54b81abe617a5f386887c31dbfebcaf4ff3c Mon Sep 17 00:00:00 2001 From: Nanley Chery Date: Wed, 23 Nov 2022 16:20:43 -0800 Subject: [PATCH] docs: Document the implicit barriers around blits MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 Part-of: --- docs/gallium/context.rst | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/gallium/context.rst b/docs/gallium/context.rst index 5ae3354d53e..0b1630d57c9 100644 --- a/docs/gallium/context.rst +++ b/docs/gallium/context.rst @@ -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