vkCmdCopyMemoryIndirectNV - Copy data between memory regions

Description

Each region read from copyBufferAddress is copied from the source region to the specified destination region. The results are undefined if any of the source and destination regions overlap in memory.

Valid Usage

• The indirectCopy feature must be enabled

• copyBufferAddress must be 4 byte aligned
• stride must be a multiple of 4 and must be greater than or equal to sizeof(CopyMemoryIndirectCommandNV)
• The CommandPool that commandBuffer was allocated from must support at least one of the PhysicalDeviceCopyMemoryIndirectPropertiesNV::supportedQueues

Valid Usage (Implicit)

• commandBuffer must be a valid CommandBuffer handle

• commandBuffer must be in the recording state
• The CommandPool that commandBuffer was allocated from must support transfer, graphics, or compute operations
• This command must only be called outside of a render pass instance
• This command must only be called outside of a video coding scope

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

'

See Also

VK_NV_copy_memory_indirect, CommandBuffer, DeviceAddress

vkCmdCopyMemoryToImageIndirectNV - Copy data from a memory region into an image

Description

Each region in copyBufferAddress is copied from the source memory region to an image region in the destination image. If the destination image is of type IMAGE_TYPE_3D, the starting slice and number of slices to copy are specified in pImageSubresources::baseArrayLayer and pImageSubresources::layerCount respectively. The copy must be performed on a queue that supports indirect copy operations, see PhysicalDeviceCopyMemoryIndirectPropertiesNV.

Valid Usage

• The indirectCopy feature must be enabled

• dstImage must not be a protected image
• The aspectMask member for every subresource in pImageSubresources must only have a single bit set
• The image region specified by each element in copyBufferAddress must be a region that is contained within dstImage
• dstImage must have been created with IMAGE_USAGE_TRANSFER_DST_BIT usage flag
• If dstImage is non-sparse then it must be bound completely and contiguously to a single DeviceMemory object
• dstImage must have a sample count equal to SAMPLE_COUNT_1_BIT
• dstImageLayout must specify the layout of the image subresources of dstImage at the time this command is executed on a Device
• dstImageLayout must be IMAGE_LAYOUT_TRANSFER_DST_OPTIMAL, IMAGE_LAYOUT_SHARED_PRESENT_KHR, or IMAGE_LAYOUT_GENERAL
• The specified mipLevel of each region must be less than the mipLevels specified in ImageCreateInfo when dstImage was created
• If the maintenance5 feature is not enabled, layerCount must not be REMAINING_ARRAY_LAYERS
• If layerCount is not REMAINING_ARRAY_LAYERS, the specified baseArrayLayer + layerCount of each region must be less than or equal to the arrayLayers specified in ImageCreateInfo when dstImage was created
• The imageOffset and imageExtent members of each region must respect the image transfer granularity requirements of commandBuffer’s command pool’s queue family, as described in QueueFamilyProperties
• dstImage must not have been created with flags containing IMAGE_CREATE_SUBSAMPLED_BIT_EXT
• If the queue family used to create the CommandPool which commandBuffer was allocated from does not support QUEUE_GRAPHICS_BIT, for each region, the aspectMask member of pImageSubresources must not be IMAGE_ASPECT_DEPTH_BIT or IMAGE_ASPECT_STENCIL_BIT
• For each region in copyBufferAddress, imageOffset.y and (imageExtent.height + imageOffset.y) must both be greater than or equal to 0 and less than or equal to the height of the specified subresource
• offset must be 4 byte aligned
• stride must be a multiple of 4 and must be greater than or equal to sizeof(CopyMemoryToImageIndirectCommandNV)

Valid Usage (Implicit)

• commandBuffer must be a valid CommandBuffer handle

• dstImage must be a valid Image handle
• dstImageLayout must be a valid ImageLayout value
• pImageSubresources must be a valid pointer to an array of copyCount valid ImageSubresourceLayers structures
• commandBuffer must be in the recording state
• The CommandPool that commandBuffer was allocated from must support transfer, graphics, or compute operations
• This command must only be called outside of a render pass instance
• This command must only be called outside of a video coding scope
• copyCount must be greater than 0
• Both of commandBuffer, and dstImage 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

'

See Also

VK_NV_copy_memory_indirect, CommandBuffer, DeviceAddress, Image, ImageLayout, ImageSubresourceLayers

VkCopyMemoryIndirectCommandNV - Structure specifying indirect memory region copy operation

Valid Usage

• The srcAddress must be 4 byte aligned

• The dstAddress must be 4 byte aligned
• The size must be 4 byte aligned

See Also

VK_NV_copy_memory_indirect, DeviceAddress, DeviceSize

VkCopyMemoryToImageIndirectCommandNV - Structure specifying indirect buffer image copy operation

Valid Usage

• The srcAddress must be 4 byte aligned

• bufferRowLength must be 0, or greater than or equal to the width member of imageExtent
• bufferImageHeight must be 0, or greater than or equal to the height member of imageExtent
• imageOffset must specify a valid offset in the destination image
• imageExtent must specify a valid region in the destination image and can be 0

Valid Usage (Implicit)

• imageSubresource must be a valid ImageSubresourceLayers structure

See Also

VK_NV_copy_memory_indirect, DeviceAddress, Extent3D, ImageSubresourceLayers, Offset3D

VkPhysicalDeviceCopyMemoryIndirectFeaturesNV - Structure describing indirect copy features supported by an implementation

Members

This structure describes the following features:

Description

If the PhysicalDeviceCopyMemoryIndirectFeaturesNV 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. PhysicalDeviceCopyMemoryIndirectFeaturesNV can also be used in the pNext chain of DeviceCreateInfo to selectively enable these features.

Valid Usage (Implicit)

See Also

VK_NV_copy_memory_indirect, Bool32, StructureType

VkPhysicalDeviceCopyMemoryIndirectPropertiesNV - Structure describing supported queues for indirect copy

Description

If the indirectCopy feature is supported, supportedQueues must return at least one supported queue.

If the PhysicalDeviceCopyMemoryIndirectPropertiesNV structure is included in the pNext chain of the PhysicalDeviceProperties2 structure passed to getPhysicalDeviceProperties2, it is filled in with each corresponding implementation-dependent property.

Valid Usage (Implicit)

See Also

VK_NV_copy_memory_indirect, QueueFlags, StructureType