vkCmdUpdatePipelineIndirectBufferNV - Update the indirect compute pipeline’s metadata

Description

cmdUpdatePipelineIndirectBufferNV is only allowed outside of a render pass. This command is treated as a “transfer” operation for the purposes of synchronization barriers. The writes to the address must be synchronized using stages PIPELINE_STAGE_2_COPY_BIT and PIPELINE_STAGE_COMMAND_PREPROCESS_BIT_NV and with access masks ACCESS_MEMORY_WRITE_BIT and ACCESS_COMMAND_PREPROCESS_READ_BIT_NV respectively before using the results in preprocessing.

Valid Usage

• pipelineBindPoint must be PIPELINE_BIND_POINT_COMPUTE

• pipeline must have been created with PIPELINE_CREATE_INDIRECT_BINDABLE_BIT_NV flag set
• pipeline must have been created with ComputePipelineIndirectBufferInfoNV structure specifying a valid address where its metadata will be saved
• The ::deviceGeneratedComputePipelines feature must be enabled

Valid Usage (Implicit)

• commandBuffer must be a valid CommandBuffer handle

• pipelineBindPoint must be a valid PipelineBindPoint value
• pipeline must be a valid Pipeline handle
• commandBuffer must be in the recording state
• The CommandPool that commandBuffer was allocated from must support QUEUE_COMPUTE_BIT, QUEUE_GRAPHICS_BIT, or QUEUE_TRANSFER_BIT operations
• This command must only be called outside of a render pass instance
• This command must not be called between suspended render pass instances
• This command must only be called outside of a video coding scope
• Both of commandBuffer, and pipeline must have been created, allocated, or retrieved from the same Device

Host Synchronization

• Host access to commandBuffer must be externally synchronized

• Host access to the CommandPool that commandBuffer was allocated from must be externally synchronized

Command Properties

'

Conditional Rendering

vkCmdUpdatePipelineIndirectBufferNV is not affected by conditional rendering

See Also

VK_NV_device_generated_commands_compute, CommandBuffer, Pipeline, PipelineBindPoint

vkGetPipelineIndirectMemoryRequirementsNV - Get the memory requirements for the compute indirect pipeline

Description

If pCreateInfo->pNext chain includes a pointer to a ComputePipelineIndirectBufferInfoNV structure, then the contents of that structure are ignored.

Valid Usage

• The ::deviceGeneratedComputePipelines feature must be enabled

• pCreateInfo->flags must include PIPELINE_CREATE_INDIRECT_BINDABLE_BIT_NV

Valid Usage (Implicit)

• device must be a valid Device handle

• pCreateInfo must be a valid pointer to a valid ComputePipelineCreateInfo structure
• pMemoryRequirements must be a valid pointer to a MemoryRequirements2 structure

See Also

VK_NV_device_generated_commands_compute, ComputePipelineCreateInfo, Device, MemoryRequirements2

vkGetPipelineIndirectDeviceAddressNV - Get pipeline’s 64-bit device address

Valid Usage

• The ::deviceGeneratedComputePipelines feature must be enabled

Valid Usage (Implicit)

• device must be a valid Device handle

• pInfo must be a valid pointer to a valid PipelineIndirectDeviceAddressInfoNV structure

See Also

VK_NV_device_generated_commands_compute, Device, PipelineIndirectDeviceAddressInfoNV

VkComputePipelineIndirectBufferInfoNV - Structure describing the device address where pipeline’s metadata will be saved

Description

If pipelineDeviceAddressCaptureReplay is zero, no specific address is requested. If pipelineDeviceAddressCaptureReplay is not zero, then it must be an address retrieved from an identically created pipeline on the same implementation. The pipeline metadata must also be placed on an identically created buffer and at the same offset using the cmdUpdatePipelineIndirectBufferNV command.

Valid Usage

• The ::deviceGeneratedComputePipelines feature must be enabled

• The pipeline creation flags in ComputePipelineCreateInfo::flags must include PIPELINE_CREATE_INDIRECT_BINDABLE_BIT_NV
• deviceAddress must be aligned to the MemoryRequirements2::memoryRequirements.alignment, as returned by getPipelineIndirectMemoryRequirementsNV
• deviceAddress must have been allocated from a buffer that was created with both the BUFFER_USAGE_TRANSFER_DST_BIT and BUFFER_USAGE_INDIRECT_BUFFER_BIT usage flags set
• size must be greater than or equal to the MemoryRequirements2::memoryRequirements.size, as returned by getPipelineIndirectMemoryRequirementsNV
• If pipelineDeviceAddressCaptureReplay is non-zero then the ::deviceGeneratedComputeCaptureReplay feature must be enabled
• If pipelineDeviceAddressCaptureReplay is non-zero then that address must have been allocated with flag MEMORY_ALLOCATE_DEVICE_ADDRESS_CAPTURE_REPLAY_BIT set
• If pipelineDeviceAddressCaptureReplay is non-zero, the pipeline must have been recreated for replay
• pipelineDeviceAddressCaptureReplay must satisfy the alignment and size requirements similar to deviceAddress

Valid Usage (Implicit)

• sType must be STRUCTURE_TYPE_COMPUTE_PIPELINE_INDIRECT_BUFFER_INFO_NV

• deviceAddress must be a valid DeviceAddress value
• If pipelineDeviceAddressCaptureReplay is not 0, pipelineDeviceAddressCaptureReplay must be a valid DeviceAddress value

See Also

VK_NV_device_generated_commands_compute, DeviceAddress, DeviceSize, StructureType

VkPhysicalDeviceDeviceGeneratedCommandsComputeFeaturesNV - Structure describing the device-generated compute features that can be supported by an implementation

Members

This structure describes the following features:

Description

If the PhysicalDeviceDeviceGeneratedCommandsComputeFeaturesNV structure is included in the pNext chain of the PhysicalDeviceFeatures2 structure passed to getPhysicalDeviceFeatures2, it is filled in to indicate whether each corresponding feature is supported. If the application wishes to use a Device with any features described by PhysicalDeviceDeviceGeneratedCommandsComputeFeaturesNV, it must add an instance of the structure, with the desired feature members set to TRUE, to the pNext chain of DeviceCreateInfo when creating the Device.

Valid Usage (Implicit)

See Also

VK_NV_device_generated_commands_compute, Bool32, StructureType

VkPipelineIndirectDeviceAddressInfoNV - Structure specifying the pipeline to query an address for

Valid Usage

• The provided pipelineBindPoint must be of type PIPELINE_BIND_POINT_COMPUTE

• pipeline must have been created with flag PIPELINE_CREATE_INDIRECT_BINDABLE_BIT_NV set
• pipeline must have been created with a ComputePipelineIndirectBufferInfoNV structure specifying a valid address where its metadata will be saved

Valid Usage (Implicit)

• sType must be STRUCTURE_TYPE_PIPELINE_INDIRECT_DEVICE_ADDRESS_INFO_NV

• pNext must be NULL
• pipelineBindPoint must be a valid PipelineBindPoint value
• pipeline must be a valid Pipeline handle

See Also

VK_NV_device_generated_commands_compute, Pipeline, PipelineBindPoint, StructureType, getPipelineIndirectDeviceAddressNV

VkBindPipelineIndirectCommandNV - Structure specifying input data for the compute pipeline dispatch token

Valid Usage

• The ::deviceGeneratedComputePipelines feature must be enabled

• The referenced pipeline must have been created with PIPELINE_CREATE_INDIRECT_BINDABLE_BIT_NV
• The referenced pipeline must have been updated with cmdUpdatePipelineIndirectBufferNV
• The referenced pipeline’s address must have been queried with getPipelineIndirectDeviceAddressNV

Valid Usage (Implicit)

• pipelineAddress must be a valid DeviceAddress value

See Also

VK_NV_device_generated_commands_compute, DeviceAddress

VkIndirectCommandsTokenTypeNV - Enum specifying token commands

Description

'

Supported Indirect Command Tokens

See Also

VK_NV_device_generated_commands, IndirectCommandsLayoutTokenNV