mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-02-25 12:35:11 +00:00
59750fe4c7
* 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>>`
94 lines
3.1 KiB
Plaintext
94 lines
3.1 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_semaphore_win32.txt[]
|
|
|
|
*Last Modified Date*::
|
|
2016-10-21
|
|
*IP Status*::
|
|
No known IP claims.
|
|
*Contributors*::
|
|
- James Jones, NVIDIA
|
|
- Jeff Juliano, NVIDIA
|
|
- Carsten Rohde, NVIDIA
|
|
|
|
An application using external memory may wish to synchronize access to that
|
|
memory using semaphores.
|
|
This extension enables an application to export semaphore payload to and
|
|
import semaphore payload from Windows handles.
|
|
|
|
=== New Object Types
|
|
|
|
None.
|
|
|
|
=== New Enum Constants
|
|
|
|
* ename:VK_STRUCTURE_TYPE_IMPORT_SEMAPHORE_WIN32_HANDLE_INFO_KHR
|
|
* ename:VK_STRUCTURE_TYPE_EXPORT_SEMAPHORE_WIN32_HANDLE_INFO_KHR
|
|
* ename:VK_STRUCTURE_TYPE_D3D12_FENCE_SUBMIT_INFO_KHR
|
|
* ename:VK_STRUCTURE_TYPE_SEMAPHORE_GET_WIN32_HANDLE_INFO_KHR
|
|
|
|
=== New Enums
|
|
|
|
None.
|
|
|
|
=== New Structs
|
|
|
|
* slink:VkImportSemaphoreWin32HandleInfoKHR
|
|
* slink:VkExportSemaphoreWin32HandleInfoKHR
|
|
* slink:VkD3D12FenceSubmitInfoKHR
|
|
* slink:VkSemaphoreGetWin32HandleInfoKHR
|
|
|
|
=== New Functions
|
|
|
|
* flink:vkImportSemaphoreWin32HandleKHR
|
|
* flink:vkGetSemaphoreWin32HandleKHR
|
|
|
|
=== Issues
|
|
|
|
1) Do applications need to call code:CloseHandle() on the values returned
|
|
from flink:vkGetSemaphoreWin32HandleKHR when pname:handleType is
|
|
ename:VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_WIN32_BIT_KHR?
|
|
|
|
*RESOLVED*: Yes, unless it is passed back in to another driver instance to
|
|
import the object.
|
|
A successful get call transfers ownership of the handle to the application.
|
|
Destroying the semaphore object will not destroy the handle or the handle's
|
|
reference to the underlying semaphore resource.
|
|
|
|
2) Should the language regarding KMT/Windows 7 handles be moved to a
|
|
separate extension so that it can be deprecated over time?
|
|
|
|
*RESOLVED*: No.
|
|
Support for them can be deprecated by drivers if they choose, by no longer
|
|
returning them in the supported handle types of the instance level queries.
|
|
|
|
3) Should applications be allowed to specify additional object attributes
|
|
for shared handles?
|
|
|
|
*RESOLVED*: Yes.
|
|
Applications will be allowed to provide similar attributes to those they
|
|
would to any other handle creation API.
|
|
|
|
4) How do applications communicate the desired fence values to use with
|
|
etext:D3D12_FENCE-based Vulkan semaphores?
|
|
|
|
*RESOLVED*: There are a couple of options.
|
|
The values for the signaled and reset states could be communicated up front
|
|
when creating the object and remain static for the life of the Vulkan
|
|
semaphore, or they could be specified using auxiliary structures when
|
|
submitting semaphore signal and wait operations, similar to what is done
|
|
with the keyed mutex extensions.
|
|
The latter is more flexible and consistent with the keyed mutex usage, but
|
|
the former is a much simpler API.
|
|
|
|
Since Vulkan tends to favor flexibility and consistency over simplicity, a
|
|
new structure specifying D3D12 fence acquire and release values is added to
|
|
the flink:vkQueueSubmit function.
|
|
|
|
=== Version History
|
|
|
|
* Revision 1, 2016-10-21 (James Jones)
|
|
- Initial revision
|