public class AMDBufferMarker
extends java.lang.Object
VkBuffer object.
The primary purpose of these markers is to facilitate the development of debugging tools for tracking which pipelined command contributed to device loss.
None.
VK_AMD_buffer_marker| Modifier and Type | Field and Description |
|---|---|
static java.lang.String |
VK_AMD_BUFFER_MARKER_EXTENSION_NAME
The extension name.
|
static int |
VK_AMD_BUFFER_MARKER_SPEC_VERSION
The extension specification version.
|
| Modifier and Type | Method and Description |
|---|---|
static void |
vkCmdWriteBufferMarkerAMD(org.lwjgl.vulkan.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_VERSION
public static final java.lang.String VK_AMD_BUFFER_MARKER_EXTENSION_NAME
public static void vkCmdWriteBufferMarkerAMD(org.lwjgl.vulkan.VkCommandBuffer commandBuffer,
int pipelineStage,
long dstBuffer,
long dstOffset,
int marker)
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 vkCmdWriteBufferMarkerAMD commands so long as their specified pipeline stages occur either at the same time or earlier than this command's specified pipelineStage.
While consecutive buffer marker writes with the same pipelineStage parameter 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 pipelineStage and PIPELINE_STAGE_TRANSFER_BIT.
Similar to vkCmdWriteTimestamp, if an implementation is unable to write a marker at any specific pipeline stage, it may instead do so at any logically later stage.
Implementations may only support a limited number of pipelined marker write operations in flight at a given time, thus excessive number of marker write operations may degrade command execution performance.
dstOffset must be less than or equal to the size of dstBuffer minus 4.dstBuffer must have been created with BUFFER_USAGE_TRANSFER_DST_BIT usage flagdstBuffer is non-sparse then it must be bound completely and contiguously to a single VkDeviceMemory objectdstOffset must be a multiple of 4commandBuffer must be a valid VkCommandBuffer handlepipelineStage must be a valid VkPipelineStageFlagBits valuedstBuffer must be a valid VkBuffer handlecommandBuffer must be in the recording stateVkCommandPool that commandBuffer was allocated from must support transfer, graphics, or compute operationscommandBuffer, and dstBuffer must have been created, allocated, or retrieved from the same VkDevicecommandBuffer must be externally synchronizedVkCommandPool that commandBuffer was 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 VkPipelineStageFlagBits values, 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.Copyright LWJGL. All Rights Reserved. License terms.