[Mesa-dev] [PATCH 0/7] anv: Implement the VK_KHX_external_memory extensions

[Chad Versace]

For anyone reading the new extension specs and asking "Wait? What's this
OPAQUE_FD thing? And why do we have memory import/export for Win32
handles but not for dma_bufs?".

There does exist a dma_buf extension, VK_MESAX_external_memory_dma_buf,
that can do negotiation on DRM format modifiers.  It's a rough draft.
I'm adding some last-minute polish to it, and then will push it
somewhere public asap.

On Mon 27 Feb 2017, Jason Ekstrand wrote:
> This patch series is an initial implementation of the newly released
> VK_KHX_external_memory extension family.  These extensions add experimental
> support image and memory sharing between two Vulkan instances.  Since
> they're experimental, it's a bit up-for-debate as to whether or not we
> should actually merge them into master.  This cover letter seems as good a
> place as any to hold that discussion. :-)
> 
> Chad Versace (1):
>   anv: Implement VK_KHX_external_memory_capabilities
> 
> Jason Ekstrand (6):
>   anv: Add the pci_id into the shader cache UUID
>   anv: Refactor device_get_cache_uuid into physical_device_init_uuids
>   anv/physical_device: Rename uuid to pipeline_cache_uuid
>   util/vk: Add helpers for finding an extension struct
>   anv: Implement VK_KHX_external_memory
>   anv: Implement VK_KHX_external_memory_fd
> 
>  src/intel/vulkan/anv_device.c           | 186 +++++++++++++++++++++++++++-----
>  src/intel/vulkan/anv_entrypoints_gen.py |   3 +
>  src/intel/vulkan/anv_formats.c          |  78 +++++++++++++-
>  src/intel/vulkan/anv_pipeline_cache.c   |   4 +-
>  src/intel/vulkan/anv_private.h          |   4 +-
>  src/util/vk_util.h                      |  17 +++
>  6 files changed, 261 insertions(+), 31 deletions(-)
> 
> -- 
> 2.5.0.400.gff86faf
> 
> _______________________________________________
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/mesa-dev