mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-02-25 12:35:11 +00:00
194a7f4d0d
* Update release number to 122.
Internal Issues:
* Add style guide language on not using standalone `+` signs (internal
issue 736); not using leading whitespace for markup (internal issue
747); and on keeping descriptions of a single API in a contiguous block
of markup (internal issue 949), and apply them to the specification.
* Add a glossary definition of "`constant integral expression`", pointing
to the SPIR-V "`constant instruction`" definition (internal issue 1225).
* Many minor edits to improve writing style consistency and capture
additional style guidelines (internal issue 1553).
* Clarify that <<fragops-depth-write, depth writes are not performed>> if
there is no depth framebuffer attachment (internal issue 1771).
* Allow implementations to use rectangular line style of interpolation for
<<primsrast-lines-bresenham, wide Bresenham lines>>, though replicating
attributes is still preferred. Clarify that code:FragCoord is not
replicated (internal issue 1772).
* Resolve a contradiction in valid usage statements for
slink:VkImageCreateInfo and slink:VkImageStencilUsageCreateInfoEXT
(internal issue 1773).
* Add style guide discussion of markup for indented equations, and use
markup workaround for asciidoctor 2 compatibility (internal issue 1793).
* Deprecate the `<<VK_EXT_validation_flags>>` extension in `vk.xml` and
the extension appendix (internal issue 1801).
* Add a new checker script `scripts/xml_consistency.py`. This is not
currently run as part of internal CI (internal merge request 3285).
* Correct "`an`" -> "`a`" prepositions where needed (internal merge
request 3334).
* Clarify that the <<features-uniformBufferStandardLayout,
pname:uniformBufferStandardLayout>> feature is only required when the
extension defining it is supported (internal merge request 3341).
* Bring scripts into closer sync with OpenXR, mainly through conversion of
comments to docstrings where appropriate, and add gen-scripts-docs.sh
(internal merge request 3324).
* Correct pname:maxDrawMeshTasksCount to 2^16^-1 in the <<limits-required,
Required Limits>> table (internal merge requests 3361).
New Extensions
* `<<VK_IMG_format_pvrtc>>` (public issue 512).
61 lines
2.1 KiB
Plaintext
61 lines
2.1 KiB
Plaintext
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 containing 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
|
|
`<<VK_KHR_external_memory_fd>>`, is sufficient to bind a slink:VkBuffer to
|
|
dma_buf.
|
|
--
|
|
|
|
=== Version History
|
|
|
|
* Revision 1, 2017-10-10 (Chad Versace)
|
|
- Squashed internal revisions
|