C Specification
To write a 32-bit marker value into memory as a pipelined operation, call:
// Provided by VK_KHR_device_address_commands with VK_AMD_buffer_marker
void vkCmdWriteMarkerToMemoryAMD(
VkCommandBuffer commandBuffer,
const VkMemoryMarkerInfoAMD* pInfo);Parameters
-
commandBufferis the command buffer into which the command will be recorded. -
pInfospecifies a pointer to an VkMemoryMarkerInfoAMD structure defining parameters of this command.
Description
When vkCmdWriteMarkerToMemoryAMD is submitted to a queue, it defines
an execution dependency between prior operations and writing the marker
value, as well as a memory dependency from earlier
buffer marker write commands.
The first synchronization scope
includes operations performed by operations that occur earlier in
submission order in the pipeline stage
identified by pInfo->stage.
It additionally includes other buffer marker write
commands that occur earlier in submission order that specified either the same pInfo->stage or a
stage that is logically earlier.
The second synchronization scope includes only the buffer marker write.
The first access scope includes only accesses performed by other buffer marker write commands.
The second access scope is empty.
The access scope for buffer marker writes falls under the
VK_ACCESS_TRANSFER_WRITE_BIT flag, and is performed by either
pInfo->stage or VK_PIPELINE_STAGE_TRANSFER_BIT.
Synchronization commands should specify this access
flag and both pipeline stages when defining dependencies with this command.
|
Note
|
Similar to |
|
Note
|
Implementations may only support a limited number of pipelined marker write operations in flight at a given time. Thus an excessive number of marker write operations may degrade command execution performance. |
Document Notes
For more information, see the Vulkan Specification.
This page is extracted from the Vulkan Specification. Fixes and changes should be made to the Specification, not directly.