Lines Matching refs:dispatchable

52 call and is a dispatchable object (see Vulkan specification section 2.2 Object
53 Model).  Under the covers, the dispatchable object handle is a pointer to a
230 that uses a VkDevice as the first parameter or a dispatchable object that is a
510   which contain no dispatchable object as the first parameter, such as
515   first parameter dispatchable object. Both core entry points and any instance
518   use new instance level dispatchable objects other than VkInstance and
520   defined dispatchable objects must be queryable via
568 within Vulkan dispatchable objects, which include VkInstance, VkPhysicalDevice,
570 dispatchable objects created by ICDs are as follows:
572 - All dispatchable objects created by an ICD can be cast to void \*\*
577 1. The ICD must return a pointer for the opaque dispatchable object handle.
586    dispatchable objects, as follows (see include/vulkan/vk\_icd.h):
1020 Instance level Vulkan commands are those that have the dispatchable objects
1026 extensions may introduce new instance or device level dispatchable objects, so
1258 supports layers wrapping any Vulkan object including dispatchable objects.
1262 layer will see the wrapped object. Layers which wrap dispatchable objects must
1264 as defined in vk_layer.h. Specifically, an instance wrapped dispatchable object
1272 A device wrapped dispatchable object could be as follows:
1282 dispatchable objects at a given level (eg device or instance) the layer may
1284 there are multiple dispatchable objects for a given VkInstance or VkDevice, the
1289 Layers which create dispatchable objects take special care. Remember that loader
1293 dispatchable object without loader trampoline code is as follows:
1294 - object wrapping layers that wrap dispatchable objects
1295 - layers which add extensions that create dispatchable objects
1298 - ICDs which add extensions that create dispatchable objects
1300 To fill in the dispatch table pointer in newly created dispatchable object,