mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-02-25 12:35:11 +00:00
* Update release number to 121. Github Issues: * Add missing `structextends` attribute in `vk.xml` for slink:VkPhysicalDevicePipelineExecutablePropertiesFeaturesKHR (public issue 1018). * Change attributes of flink:vkCmdCopyAccelerationStructureNV, flink:vkCmdWriteAccelerationStructuresPropertiesNV, flink:vkCmdBuildAccelerationStructureNV, and flink:vkCmdTraceRaysNV to require that these commands execute outside renderpasses (public issue 1021). * Add an issue to the `<<VK_EXT_buffer_device_address>>` appendix discussing the introduction of new names and aliasing by equivalent old names (public pull request 1024). Internal Issues: * Protect the `VK_KHR_sampler_mirror_clamp_to_edge` extension with asciidoctor conditionals, and remove it from the core-only specification builds, where it had previously been force-included in the Makefile. It is now treated like any other extension (internal issue 1776). * Edit some asciidoctor anchor names starting with `features-features-` to just start with `features-`, since the old chapters was split into 3 pieces. There are still some mild naming inconsistencies with anchors which may be addressed in the future (internal issue 1792). * Add `KHR` alias for the non-suffixed extension token ename:VK_SAMPLER_ADDRESS_MODE_MIRROR_CLAMP_TO_EDGE, for compatibility with naming rules for extensions (internal issue 1796). * Clarify requirements for external memory in NOTEs for sname:VkExternalMemoryBufferCreateInfo, and valid usage statements for flink:vkBindBufferMemory, slink:VkBindBufferMemoryInfo, flink:vkBindImageMemory, and slink:VkBindImageMemoryInfo (internal merge request 3301). * Make extension version numbers in `vk.xml` and extension appendices consistent. In a few cases, we could not recover history at this granularity, and left the summary of a version's change undefined (internal merge request 3323). * Fix invocation of `CodeInlineMacro` in the Ruby extension backing the `code:` macro, which was delegating to the wrong base class (internal merge request 3331). * Modify `reg.py` to do a better job of recognizing equivalent <enum> definitions. * Add a `sortorder` attribute to XML feature and extension tags. New Extensions * `<<VK_AMD_device_coherent_memory>>`
71 lines
1.9 KiB
Plaintext
71 lines
1.9 KiB
Plaintext
// Copyright (c) 2016-2019 Khronos Group. This work is licensed under a
|
|
// Creative Commons Attribution 4.0 International License; see
|
|
// http://creativecommons.org/licenses/by/4.0/
|
|
|
|
include::meta/VK_KHR_external_fence_win32.txt[]
|
|
|
|
*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_win32>>`
|
|
|
|
An application using external memory may wish to synchronize access to that
|
|
memory using fences.
|
|
This extension enables an application to export fence payload to and import
|
|
fence payload from Windows handles.
|
|
|
|
=== New Object Types
|
|
|
|
None.
|
|
|
|
=== New Enum Constants
|
|
|
|
* ename:VK_STRUCTURE_TYPE_IMPORT_FENCE_WIN32_HANDLE_INFO_KHR
|
|
* ename:VK_STRUCTURE_TYPE_EXPORT_FENCE_WIN32_HANDLE_INFO_KHR
|
|
* ename:VK_STRUCTURE_TYPE_FENCE_GET_WIN32_HANDLE_INFO_KHR
|
|
|
|
=== New Enums
|
|
|
|
None.
|
|
|
|
=== New Structs
|
|
|
|
* slink:VkImportFenceWin32HandleInfoKHR
|
|
* slink:VkExportFenceWin32HandleInfoKHR
|
|
* slink:VkFenceGetWin32HandleInfoKHR
|
|
|
|
=== New Functions
|
|
|
|
* flink:vkImportFenceWin32HandleKHR
|
|
* flink:vkGetFenceWin32HandleKHR
|
|
|
|
=== Issues
|
|
|
|
This extension borrows concepts, semantics, and language from
|
|
`<<VK_KHR_external_semaphore_win32>>`.
|
|
That extension's issues apply equally to this extension.
|
|
|
|
1) Should D3D12 fence handle types be supported, like they are for
|
|
semaphores?
|
|
|
|
*RESOLVED*: No.
|
|
Doing so would require extending the fence signal and wait operations to
|
|
provide values to signal / wait for, like sname:VkD3D12FenceSubmitInfoKHR
|
|
does.
|
|
A D3D12 fence can be signaled by importing it into a slink:VkSemaphore
|
|
instead of a slink:VkFence, and applications can check status or wait on the
|
|
D3D12 fence using non-Vulkan APIs.
|
|
The convenience of being able to do these operations on sname:VkFence
|
|
objects doesn't justify the extra API complexity.
|
|
|
|
=== Version History
|
|
|
|
* Revision 1, 2017-05-08 (Jesse Hall)
|
|
- Initial revision
|