2017-11-27 09:07:06 +00:00
|
|
|
include::meta/VK_EXT_external_memory_dma_buf.txt[]
|
|
|
|
|
|
|
|
*Last Modified Date*::
|
|
|
|
2017-10-10
|
|
|
|
*IP Status*::
|
|
|
|
No known IP claims.
|
|
|
|
*Contributors*::
|
|
|
|
- Chad Versace, Google
|
|
|
|
- James Jones, NVIDIA
|
|
|
|
- Jason Ekstrand, Intel
|
|
|
|
|
|
|
|
A dma_buf is a type of file descriptor, defined by the Linux kernel, that
|
|
|
|
allows sharing memory across kernel device drivers and across processes.
|
|
|
|
This extension enables applications to import a dma_buf as
|
|
|
|
slink:VkDeviceMemory; to export slink:VkDeviceMemory as a dma_buf; and to
|
|
|
|
create slink:VkBuffer objects that can: be bound to that memory.
|
|
|
|
|
|
|
|
=== New Enum Constants
|
|
|
|
|
|
|
|
* Extending elink:VkExternalMemoryHandleTypeFlagBitsKHR:
|
|
|
|
** ename:VK_EXTERNAL_MEMORY_HANDLE_TYPE_DMA_BUF_BIT_EXT
|
|
|
|
|
|
|
|
=== Issues
|
|
|
|
|
|
|
|
1.
|
|
|
|
How does the application, when creating a slink:VkImage that it intends
|
|
|
|
to bind to dma_buf slink:VkDeviceMemory that contains an externally
|
|
|
|
produced image, specify the memory layout (such as row pitch and DRM
|
|
|
|
format modifier) of the slink:VkImage? In other words, how does the
|
|
|
|
application achieve behavior comparable to that provided by
|
|
|
|
https://www.khronos.org/registry/EGL/extensions/EXT/EGL_EXT_image_dma_buf_import.txt[EGL_EXT_image_dma_buf_import]
|
|
|
|
and
|
|
|
|
https://www.khronos.org/registry/EGL/extensions/EXT/EGL_EXT_image_dma_buf_import_modifiers.txt[EGL_EXT_image_dma_buf_import_modifiers]?
|
|
|
|
+
|
|
|
|
--
|
|
|
|
*RESOLVED*.
|
|
|
|
Features comparable to those in
|
|
|
|
https://www.khronos.org/registry/EGL/extensions/EXT/EGL_EXT_image_dma_buf_import.txt[EGL_EXT_image_dma_buf_import]
|
|
|
|
and
|
|
|
|
https://www.khronos.org/registry/EGL/extensions/EXT/EGL_EXT_image_dma_buf_import_modifiers.txt[EGL_EXT_image_dma_buf_import_modifiers]
|
|
|
|
will be provided by an extension layered atop this one.
|
|
|
|
--
|
|
|
|
|
|
|
|
2.
|
|
|
|
Without the ability to specify the memory layout of external dma_buf
|
|
|
|
images, how is this extension useful?
|
|
|
|
+
|
|
|
|
--
|
|
|
|
*RESOLVED*.
|
|
|
|
This extension provides exactly one new feature: the ability to
|
|
|
|
import/export between dma_bufs and slink:VkDeviceMemory.
|
|
|
|
This feature, together with features provided by
|
Change log for January 5, 2018 Vulkan 1.0.67 spec update:
* Bump API patch number and header version number to 67 for this update.
* Update copyright dates to 2018
Github Issues:
* Fix texture lookup functions in `GL_KHR_vulkan_glsl` specification
(public pull request 363).
* Clarify the state waited semaphores are left in when a call to
flink:vkQueuePresentKHR fails (public issue 572).
* Cleanup descriptions of slink:VkObjectTablePushConstantEntryNVX and
slink:VkObjectTableDescriptorSetEntryNVX (public issue 583)
* Remove redundant flink:vkCmdSetDiscardRectangleEXT valid usage
statements (public pull 586).
* Make dynamic state array length valid usage statements implicit for
flink:vkCmdSetViewportWScalingNV, flink:vkCmdSetDiscardRectangleEXT, and
flink:vkCmdSetViewport (public pull 589).
* Clarify meaning of window extent (0,0) in slink:VkSwapchainKHR for the
Windows and X11 platforms, in their respective extensions (public issue
590).
* Allow flink:vkGetPastPresentationTimingGOOGLE to return
ename:VK_INCOMPLETE (public issue 604).
* Add synchronization valid usage statements to flink:vkAcquireNextImage
(public pull 611).
* Fix some broken external links and internal xrefs (public pull 613).
* Clean up slink:VkViewport valid usage statements in the presence or
absence of relevant extensions (public pull 623).
* Remove
ename:VK_IMAGE_LAYOUT_DEPTH_READ_ONLY_STENCIL_ATTACHMENT_OPTIMAL_KHR
token from VK_KHR_maintenance2 from the non-extension VU path for
slink:VkGraphicsPipelineCreateInfo (public issue 628).
* Miscellaneous minor markup fixes - extension name strings (public pull
631), Notes (pull 633), queue names emitted by generator scripts (pull
634), block formatting in slink:VkDescriptorUpdateTemplateEntryKHR (pull
635), ename:VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_CUBIC_BIT_IMG (pull
641), quotes and apostrophes (pull 643),
* Miscellaneous minor grammar fixes (public pull 644).
* Fix markup macros so usage like ptext:*Src* works (public pull 647).
Internal Issues:
* Clarify in the `VK_KHR_surface` and `VK_KHR_swapchain` extensions that
parameter combinations which aren't supported for normal images are also
unsupported for presentable images, even if the parameter values are
individually supported as reported by the surface capability queries
(internal issue 1029).
* Fixed XML typo in the valid value field of the pname:sType member of
slink:VkPhysicalDeviceExternalMemoryHostPropertiesEXT (internal issue
1100).
Other Issues:
* Add memory semantics validity rules to the <<spirvenv-module-validation,
Validation Rules within a Module>> section of the SPIR-V environment
appendix, and specify that sequentiality consistency is not supported.
This forbids certain cases like "`Load+Release`" that we don't expect to
ever be meaningful.
* Document mapping of OpenGL Shading Language barriers to SPIR-V scope and
semantics in the `GL_KHR_vulkan_glsl` specification.
New Extensions:
* `VK_EXT_conservative_rasterization`
2018-01-06 01:39:15 +00:00
|
|
|
`<<VK_KHR_external_memory_fd>>`, is sufficient to bind a slink:VkBuffer to
|
2017-11-27 09:07:06 +00:00
|
|
|
dma_buf.
|
|
|
|
--
|
|
|
|
|
|
|
|
=== Version History
|
|
|
|
|
|
|
|
* Revision 1, 2017-10-10 (Chad Versace)
|
|
|
|
- Squashed internal revisions
|