public class AMDBufferMarker extends java.lang.ObjectThis extension adds a new operation to execute pipelined writes of small marker values into a
The primary purpose of these markers is to facilitate the development of debugging tools for tracking which pipelined command contributed to device loss.
- Name String
- Extension Type
- Device extension
- Registered Extension Number
- Extension and Version Dependencies
- Requires Vulkan 1.0
- Daniel Rakos drakos-amd
- Last Modified Date
- IP Status
- No known IP claims.
- Matthaeus G. Chajdas, AMD
- Jaakko Konttinen, AMD
- Daniel Rakos, AMD
All Methods Static Methods Concrete Methods Modifier and Type Method Description
vkCmdWriteBufferMarkerAMD(VkCommandBuffer commandBuffer, int pipelineStage, long dstBuffer, long dstOffset, int marker)Execute a pipelined write of a marker value into a buffer.
public static final int VK_AMD_BUFFER_MARKER_SPEC_VERSIONThe extension specification version.
- See Also:
- Constant Field Values
public static final java.lang.String VK_AMD_BUFFER_MARKER_EXTENSION_NAMEThe extension name.
- See Also:
- Constant Field Values
public static void vkCmdWriteBufferMarkerAMD(VkCommandBuffer commandBuffer, int pipelineStage, long dstBuffer, long dstOffset, int marker)Execute a pipelined write of a marker value into a buffer.
To write a 32-bit marker value into a buffer as a pipelined operation, call:
void vkCmdWriteBufferMarkerAMD( VkCommandBuffer commandBuffer, VkPipelineStageFlagBits pipelineStage, VkBuffer dstBuffer, VkDeviceSize dstOffset, uint32_t marker);
The command will write the 32-bit marker value into the buffer only after all preceding commands have finished executing up to at least the specified pipeline stage. This includes the completion of other preceding
vkCmdWriteBufferMarkerAMDcommands so long as their specified pipeline stages occur either at the same time or earlier than this command's specified
While consecutive buffer marker writes with the same
pipelineStageparameter are implicitly complete in submission order, memory and execution dependencies between buffer marker writes and other operations must still be explicitly ordered using synchronization commands. The access scope for buffer marker writes falls under the
ACCESS_TRANSFER_WRITE_BIT, and the pipeline stages for identifying the synchronization scope must include both
dstOffsetmust be less than or equal to the size of
dstBuffermust have been created with
dstBufferis non-sparse then it must be bound completely and contiguously to a single
dstOffsetmust be a multiple of 4
Valid Usage (Implicit)
commandBuffermust be a valid
pipelineStagemust be a valid
dstBuffermust be a valid
commandBuffermust be in the recording state
commandBufferwas allocated from must support transfer, graphics, or compute operations
- Both of
dstBuffermust have been created, allocated, or retrieved from the same
- Host access to
commandBuffermust be externally synchronized
- Host access to the
commandBufferwas allocated from must be externally synchronized
Command Buffer Levels Render Pass Scope Supported Queue Types Pipeline Type Primary Secondary Both Transfer Graphics Compute Transfer
commandBuffer- the command buffer into which the command will be recorded.
pipelineStage- one of the
VkPipelineStageFlagBitsvalues, specifying the pipeline stage whose completion triggers the marker write.
dstBuffer- the buffer where the marker will be written to.
dstOffset- the byte offset into the buffer where the marker will be written to.
marker- the 32-bit value of the marker.