VkImportMemoryWin32HandleInfoKHR
To import memory from a Windows handle, add a
VkImportMemoryWin32HandleInfoKHR structure to the pNext chain of
the VkMemoryAllocateInfo structure.
The VkImportMemoryWin32HandleInfoKHR structure is defined as:
typedef struct VkImportMemoryWin32HandleInfoKHR {
VkStructureType sType;
const void* pNext;
VkExternalMemoryHandleTypeFlagBits handleType;
HANDLE handle;
LPCWSTR name;
} VkImportMemoryWin32HandleInfoKHR;
sTypeis a VkStructureType value identifying this structure.pNextisNULLor a pointer to a structure extending this structure.handleTypeis a VkExternalMemoryHandleTypeFlagBits value specifying the type ofhandleorname.handleisNULLor the external handle to import.nameisNULLor a null-terminated UTF-16 string naming the payload to import.
Importing memory object payloads from Windows handles does not transfer
ownership of the handle to the Vulkan implementation.
For handle types defined as NT handles, the application must release handle
ownership using the CloseHandle system call when the handle is no
longer needed.
For handle types defined as NT handles, the imported memory object holds a
reference to its payload.
Non-NT handle import operations do not add a reference to their associated payload. If the original object owning the payload is destroyed, all resources and handles sharing that payload will become invalid.
Applications can import the same payload into multiple instances of Vulkan,
into the same instance from which it was exported, and multiple times into a
given Vulkan instance.
In all cases, each import operation must create a distinct
VkDeviceMemory object.
Valid Usage
VUID-VkImportMemoryWin32HandleInfoKHR-handleType-00658
If handleType is not 0, it must be supported for import, as
reported by VkExternalImageFormatProperties or
VkExternalBufferProperties
VUID-VkImportMemoryWin32HandleInfoKHR-handle-00659
The memory from which handle was exported, or the memory named by
name must have been created on the same underlying physical
device as device
VUID-VkImportMemoryWin32HandleInfoKHR-handleType-00660
If handleType is not 0, it must be defined as an NT handle or a
global share handle
VUID-VkImportMemoryWin32HandleInfoKHR-handleType-01439
If handleType is not
VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_BIT,
VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_BIT,
VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_HEAP_BIT, or
VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_RESOURCE_BIT, namemust be NULL
VUID-VkImportMemoryWin32HandleInfoKHR-handleType-01440
If handleType is not 0 and handle is NULL, namemust name a valid memory resource of the type specified by
handleType
VUID-VkImportMemoryWin32HandleInfoKHR-handleType-00661
If handleType is not 0 and name is NULL, handlemust be a valid handle of the type specified by handleType
VUID-VkImportMemoryWin32HandleInfoKHR-handle-01441
If handle is not NULL, name must be NULL
VUID-VkImportMemoryWin32HandleInfoKHR-handle-01518
If handle is not NULL, it must obey any requirements listed for
handleType in
external memory handle
types compatibility
VUID-VkImportMemoryWin32HandleInfoKHR-name-01519
If name is not NULL, it must obey any requirements listed for
handleType in
external memory handle
types compatibility
Valid Usage (Implicit)
VUID-VkImportMemoryWin32HandleInfoKHR-sType-sType
sType must be VK_STRUCTURE_TYPE_IMPORT_MEMORY_WIN32_HANDLE_INFO_KHR
VUID-VkImportMemoryWin32HandleInfoKHR-handleType-parameter
If handleType is not 0, handleType must be a valid VkExternalMemoryHandleTypeFlagBits value