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>>`
79 lines
2.2 KiB
Plaintext
79 lines
2.2 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_memory_fd.txt[]
|
|
|
|
*Last Modified Date*::
|
|
2016-10-21
|
|
*IP Status*::
|
|
No known IP claims.
|
|
*Contributors*::
|
|
- James Jones, NVIDIA
|
|
- Jeff Juliano, NVIDIA
|
|
|
|
An application may wish to reference device memory in multiple Vulkan
|
|
logical devices or instances, in multiple processes, and/or in multiple
|
|
APIs.
|
|
This extension enables an application to export POSIX file descriptor
|
|
handles from Vulkan memory objects and to import Vulkan memory objects from
|
|
POSIX file descriptor handles exported from other Vulkan memory objects or
|
|
from similar resources in other APIs.
|
|
|
|
=== New Object Types
|
|
|
|
None.
|
|
|
|
=== New Enum Constants
|
|
|
|
* ename:VK_STRUCTURE_TYPE_IMPORT_MEMORY_FD_INFO_KHR
|
|
* ename:VK_STRUCTURE_TYPE_MEMORY_FD_PROPERTIES_KHR
|
|
* ename:VK_STRUCTURE_TYPE_MEMORY_GET_FD_INFO_KHR
|
|
|
|
=== New Enums
|
|
|
|
None.
|
|
|
|
=== New Structs
|
|
|
|
* slink:VkImportMemoryFdInfoKHR
|
|
* slink:VkMemoryFdPropertiesKHR
|
|
* slink:VkMemoryGetFdInfoKHR
|
|
|
|
=== New Functions
|
|
|
|
* flink:vkGetMemoryFdKHR
|
|
* flink:vkGetMemoryFdPropertiesKHR
|
|
|
|
=== Issues
|
|
|
|
1) Does the application need to close the file descriptor returned by
|
|
flink:vkGetMemoryFdKHR?
|
|
|
|
*RESOLVED*: Yes, unless it is passed back in to a driver instance to import
|
|
the memory.
|
|
A successful get call transfers ownership of the file descriptor to the
|
|
application, and a successful import transfers it back to the driver.
|
|
Destroying the original memory object will not close the file descriptor or
|
|
remove its reference to the underlying memory resource associated with it.
|
|
|
|
2) Do drivers ever need to expose multiple file descriptors per memory
|
|
object?
|
|
|
|
*RESOLVED*: No.
|
|
This would indicate there are actually multiple memory objects, rather than
|
|
a single memory object.
|
|
|
|
3) How should the valid size and memory type for POSIX file descriptor
|
|
memory handles created outside of Vulkan be specified?
|
|
|
|
*RESOLVED*: The valid memory types are queried directly from the external
|
|
handle.
|
|
The size will be specified by future extensions that introduce such external
|
|
memory handle types.
|
|
|
|
=== Version History
|
|
|
|
* Revision 1, 2016-10-21 (James Jones)
|
|
- Initial revision
|