[Mesa-dev] [PATCH v2 06/32] anv: Implement VK_EXT_external_memory_dma_buf

Chad Versace chadversary at chromium.org
Wed Nov 29 21:44:06 UTC 2017


On Tue 28 Nov 2017, Jason Ekstrand wrote:
> This is a modified version of the patch originally sent by Chad Versace.
> The primary difference is that this version claims that OPQAUE_FD and
> DMA_BUF are compatible handle types.
> ---
>  src/intel/vulkan/anv_device.c      | 13 ++++++-------
>  src/intel/vulkan/anv_extensions.py |  1 +
>  src/intel/vulkan/anv_formats.c     |  8 ++++++--
>  3 files changed, 13 insertions(+), 9 deletions(-)


> @@ -1641,9 +1641,8 @@ VkResult anv_GetMemoryFdKHR(
>  
>     assert(pGetFdInfo->sType == VK_STRUCTURE_TYPE_MEMORY_GET_FD_INFO_KHR);
>  
> -   /* We support only one handle type. */
> -   assert(pGetFdInfo->handleType ==
> -          VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_FD_BIT_KHR);
> +   assert(pGetFdInfo->handleType == VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_FD_BIT_KHR ||
> +          pGetFdInfo->handleType == VK_EXTERNAL_MEMORY_HANDLE_TYPE_DMA_BUF_BIT_EXT);
>  
>     return anv_bo_cache_export(dev, &dev->bo_cache, mem->bo, pFd);
>  }

Same as in the radv patch, anv_GetMemoryFdPropertiesKHR must be updated
for dma-buf.


More information about the mesa-dev mailing list