Safe Haskell | Safe-Inferred |
---|---|
Language | Haskell2010 |
Name
VK_KHR_win32_keyed_mutex - device extension
VK_KHR_win32_keyed_mutex
- Name String
VK_KHR_win32_keyed_mutex
- Extension Type
- Device extension
- Registered Extension Number
- 76
- Revision
- 1
- Ratification Status
- Ratified
- Extension and Version Dependencies
- VK_KHR_external_memory_win32
- Contact
Other Extension Metadata
- Last Modified Date
- 2016-10-21
- IP Status
- No known IP claims.
- Contributors
- James Jones, NVIDIA
- Jeff Juliano, NVIDIA
- Carsten Rohde, NVIDIA
Description
Applications that wish to import Direct3D 11 memory objects into the Vulkan API may wish to use the native keyed mutex mechanism to synchronize access to the memory between Vulkan and Direct3D. This extension provides a way for an application to access the keyed mutex associated with an imported Vulkan memory object when submitting command buffers to a queue.
New Structures
New Enum Constants
Version History
Revision 1, 2016-10-21 (James Jones)
- Initial revision
See Also
Win32KeyedMutexAcquireReleaseInfoKHR
Document Notes
For more information, see the Vulkan Specification
This page is a generated document. Fixes and changes should be made to the generator scripts, not directly.
Synopsis
- data Win32KeyedMutexAcquireReleaseInfoKHR = Win32KeyedMutexAcquireReleaseInfoKHR {}
- type KHR_WIN32_KEYED_MUTEX_SPEC_VERSION = 1
- pattern KHR_WIN32_KEYED_MUTEX_SPEC_VERSION :: forall a. Integral a => a
- type KHR_WIN32_KEYED_MUTEX_EXTENSION_NAME = "VK_KHR_win32_keyed_mutex"
- pattern KHR_WIN32_KEYED_MUTEX_EXTENSION_NAME :: forall a. (Eq a, IsString a) => a
Documentation
data Win32KeyedMutexAcquireReleaseInfoKHR Source #
VkWin32KeyedMutexAcquireReleaseInfoKHR - Use the Windows keyed mutex mechanism to synchronize work
Valid Usage
-
Each member of
pAcquireSyncs
andpReleaseSyncs
must be a device memory object imported by settingImportMemoryWin32HandleInfoKHR
::handleType
toEXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_BIT
orEXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_KMT_BIT
Valid Usage (Implicit)
-
If
acquireCount
is not0
,pAcquireSyncs
must be a valid pointer to an array ofacquireCount
validDeviceMemory
handles -
If
acquireCount
is not0
,pAcquireKeys
must be a valid pointer to an array ofacquireCount
uint64_t
values -
If
acquireCount
is not0
,pAcquireTimeouts
must be a valid pointer to an array ofacquireCount
uint32_t
values -
If
releaseCount
is not0
,pReleaseSyncs
must be a valid pointer to an array ofreleaseCount
validDeviceMemory
handles -
If
releaseCount
is not0
,pReleaseKeys
must be a valid pointer to an array ofreleaseCount
uint64_t
values - Both of
the elements of
pAcquireSyncs
, and the elements ofpReleaseSyncs
that are valid handles of non-ignored parameters must have been created, allocated, or retrieved from the sameDevice
See Also
Win32KeyedMutexAcquireReleaseInfoKHR | |
|
Instances
type KHR_WIN32_KEYED_MUTEX_SPEC_VERSION = 1 Source #
pattern KHR_WIN32_KEYED_MUTEX_SPEC_VERSION :: forall a. Integral a => a Source #
type KHR_WIN32_KEYED_MUTEX_EXTENSION_NAME = "VK_KHR_win32_keyed_mutex" Source #
pattern KHR_WIN32_KEYED_MUTEX_EXTENSION_NAME :: forall a. (Eq a, IsString a) => a Source #