1// Copyright (c) 2016-2018 Khronos Group. This work is licensed under a 2// Creative Commons Attribution 4.0 International License; see 3// http://creativecommons.org/licenses/by/4.0/ 4 5include::meta/VK_KHR_external_semaphore.txt[] 6 7*Last Modified Date*:: 8 2016-10-21 9*IP Status*:: 10 No known IP claims. 11*Interactions and External Dependencies*:: 12 - Promoted to Vulkan 1.1 Core 13*Contributors*:: 14 - Jason Ekstrand, Intel 15 - Jesse Hall, Google 16 - Tobias Hector, Imagination Technologies 17 - James Jones, NVIDIA 18 - Jeff Juliano, NVIDIA 19 - Matthew Netsch, Qualcomm Technologies, Inc. 20 - Ray Smith, ARM 21 - Chad Versace, Google 22 23An application using external memory may wish to synchronize access to that 24memory using semaphores. 25This extension enables an application to create semaphores from which 26non-Vulkan handles that reference the underlying synchronization primitive 27can be exported. 28 29=== New Object Types 30 31None. 32 33=== New Enum Constants 34 35 * ename:VK_STRUCTURE_TYPE_EXPORT_SEMAPHORE_CREATE_INFO_KHR 36 * ename:VK_ERROR_INVALID_EXTERNAL_HANDLE_KHR 37 38=== New Enums 39 40 * elink:VkSemaphoreImportFlagBitsKHR 41 42=== New Structs 43 44 * slink:VkExportSemaphoreCreateInfoKHR 45 46=== New Functions 47 48None. 49 50=== Promotion to Vulkan 1.1 51 52All functionality in this extension is included in core Vulkan 1.1, with the 53KHR suffix omitted. 54The original type, enum and command names are still available as aliases of 55the core functionality. 56 57=== Issues 58 591) Should there be restrictions on what side effects can occur when waiting 60on imported semaphores that are in an invalid state? 61 62*RESOLVED*: Yes. 63Normally, validating such state would be the responsibility of the 64application, and the implementation would be free to enter an undefined 65state if valid usage rules were violated. 66However, this could cause security concerns when using imported semaphores, 67as it would require the importing application to trust the exporting 68application to ensure the state is valid. 69Requiring this level of trust is undesireable for many potential use cases. 70 712) Must implementations validate external handles the application provides 72as input to semaphore state import operations? 73 74*RESOLVED*: Implementations must return an error to the application if the 75provided semaphore state handle cannot be used to complete the requested 76import operation. 77However, implementations need not validate handles are of the exact type 78specified by the application. 79