VK_KHR_external_fence_capabilities
Other Extension Metadata
Last Modified Date
2017-05-08
IP Status
No known IP claims.
Contributors
- Jesse Hall, Google
- James Jones, NVIDIA
- Jeff Juliano, NVIDIA
- Cass Everitt, Oculus
- Contributors to VK_KHR_external_semaphore_capabilities
Description
An application may wish to reference device fences in multiple Vulkan
logical devices or instances, in multiple processes, and/or in multiple
APIs.
This extension provides a set of capability queries and handle definitions
that allow an application to determine what types of external
fence
handles an implementation supports for a given set of use cases.
Promotion to Vulkan 1.1
All functionality in this extension is included in core Vulkan 1.1, with the KHR suffix omitted. The original type, enum, and command names are still available as aliases of the core functionality.
New Commands
New Structures
- VkExternalFencePropertiesKHR
- VkPhysicalDeviceExternalFenceInfoKHR
- Extending VkPhysicalDeviceProperties2:
New Enums
New Bitmasks
New Enum Constants
VK_KHR_EXTERNAL_FENCE_CAPABILITIES_EXTENSION_NAME
VK_KHR_EXTERNAL_FENCE_CAPABILITIES_SPEC_VERSION
VK_LUID_SIZE_KHR
- Extending VkExternalFenceFeatureFlagBits:
VK_EXTERNAL_FENCE_FEATURE_EXPORTABLE_BIT_KHR
VK_EXTERNAL_FENCE_FEATURE_IMPORTABLE_BIT_KHR
- Extending VkExternalFenceHandleTypeFlagBits:
VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_FD_BIT_KHR
VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_WIN32_BIT_KHR
VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT_KHR
VK_EXTERNAL_FENCE_HANDLE_TYPE_SYNC_FD_BIT_KHR
- Extending VkStructureType:
VK_STRUCTURE_TYPE_EXTERNAL_FENCE_PROPERTIES_KHR
VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_EXTERNAL_FENCE_INFO_KHR
VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_ID_PROPERTIES_KHR
Version History
- Revision 1, 2017-05-08 (Jesse Hall)
- Initial version