Lines Matching refs:ownership
2143 To avoid leaking resources, the application must: release ownership of them
2219 transfer ownership of it to the application.
2220 To avoid leaking resources, the application must: release ownership of the
2228 or transfer ownership back to Vulkan by using the file descriptor to import
2450 stext:NvSciSyncFence handle and transfer the ownership of the
2452 To avoid leaking resources, the application must: release of the ownership
2485 stext:NvSciSyncObj handle and transfer the ownership of the
2487 To avoid leaking resources, the application must: release of the ownership
2929 Importing a fence payload from Windows handles does not transfer ownership
2932 ownership using the code:CloseHandle system call when the handle is no
3023 Importing a fence payload from a file descriptor transfers ownership of the
3123 ownership of the handle to the Vulkan implementation.
3125 The application must: release ownership using the NvSciSync API when the
3159 ownership of the handle to the Vulkan implementation.
3162 The application must: release ownership using the NvSciSync API when the
3601 To avoid leaking resources, the application must: release ownership of them
3702 and transfer ownership of it to the application.
3703 To avoid leaking resources, the application must: release ownership of the
3711 or transfer ownership back to Vulkan by using the file descriptor to import
3805 event handle and transfer ownership of it to the application.
3806 To avoid leaking resources, the application must: release ownership of the
3814 descriptor, or transfer ownership back to Vulkan by using the file
3934 stext:NvSciSyncObj and transfer the ownership of the stext:NvSciSyncObj
3936 To avoid leaking resources, the application must: release ownership of the
4141 The import does not transfer the ownership of the stext:NvSciSyncObj to the
4862 ownership of the handle to the Vulkan implementation.
4864 ownership using the code:CloseHandle system call when the handle is no
4973 Importing a semaphore payload from a file descriptor transfers ownership of
5091 Importing a semaphore payload from a Zircon event handle transfers ownership
5175 ownership of the handle to the Vulkan implementation.
5177 object, the application must: release its ownership using
5178 <<NvSciSync-extension-page, NvSciSync APIs>> when that ownership is no
5596 <<synchronization-queue-transfers, Queue family ownership transfers>> and
5602 <<synchronization-queue-transfers, queue family ownership transfers>> and
5607 includes only <<synchronization-queue-transfers, queue family ownership
6171 queue family ownership transfer>> cannot: be performed using
6527 ownership between queue families>>,
6639 <<synchronization-queue-transfers, queue family ownership transfer>> for the
6673 <<synchronization-queue-transfers, queue family ownership transfer>>.
6675 <<synchronization-queue-transfers, queue family ownership transfer>>.
6722 queue family values reserved for external memory ownership transfers, as
6771 <<synchronization-queue-transfers, queue family ownership transfer>>.
6773 <<synchronization-queue-transfers, queue family ownership transfer>>.
6887 <<synchronization-queue-transfers, queue family ownership transfer>> for the
6925 <<synchronization-queue-transfers, queue family ownership transfer>>.
6927 <<synchronization-queue-transfers, queue family ownership transfer>>.
6970 queue family values reserved for external memory ownership transfers, as
7025 <<synchronization-queue-transfers, queue family ownership transfer>> or
7056 <<synchronization-queue-transfers, queue family ownership transfer>>.
7058 <<synchronization-queue-transfers, queue family ownership transfer>>.
7221 ownership transfers as the physical layout of the image will not vary
7252 ename:VK_SHARING_MODE_EXCLUSIVE must: have their ownership explicitly
7266 also explicitly manage ownership transfers between local and external queues
7309 resource between two queues in different families, but no ownership transfer
7317 when transferring from one queue family to another, then the ownership
7331 A queue family ownership transfer consists of two distinct parts:
7333 . Release exclusive ownership from the source queue family
7334 . Acquire exclusive ownership for the destination queue family
7340 release exclusive ownership of a range of a buffer or image subresource
7358 to acquire exclusive ownership of a range of a buffer or image subresource
7404 equal, no ownership transfer is performed, and the barrier operates as if
7407 Queue family ownership transfers may: perform read and write accesses on all
7411 queue family ownership transfer is executed.
7416 Once a queue family has acquired ownership of a buffer range or image
7418 contents are undefined: to other queue families unless ownership is
7430 operation_, the release and acquire operations of a queue family ownership
7435 … specifying that external memory has remained unmodified since releasing ownership',type='structs']
7438 ownership of a subresource range from one of the special queue families
7439 reserved for external memory ownership transfers described above.
7454 recent release of ownership to the queue family specified by the memory
7458 If the application releases ownership of the subresource range to one of the
7459 special queue families reserved for external memory ownership transfers with
7460 a memory barrier structure, and later re-acquires ownership from the same
7472 not a special queue family reserved for external memory ownership transfers.
7499 for external memory ownership transfers (as described in
7503 ownership to the queue family.