This extension allows applications to import CuBIN binaries and execute
them.
There is currently no specification language written for this extension.
The links to APIs defined by the extension are to stubs that only
include generated content such as API declarations and implicit valid
usage statements.
There is currently no specification language written for this type. This
section acts only as placeholder and to avoid dead links in the
specification and reference pages.
// Provided by VK_NVX_binary_import
VK_DEFINE_NON_DISPATCHABLE_HANDLE(VkCuFunctionNVX)
There is currently no specification language written for this type. This
section acts only as placeholder and to avoid dead links in the
specification and reference pages.
// Provided by VK_NVX_binary_import
VK_DEFINE_NON_DISPATCHABLE_HANDLE(VkCuModuleNVX)
There is currently no specification language written for this command.
This section acts only as placeholder and to avoid dead links in the
specification and reference pages.
There is currently no specification language written for this type. This
section acts only as placeholder and to avoid dead links in the
specification and reference pages.
There is currently no specification language written for this command.
This section acts only as placeholder and to avoid dead links in the
specification and reference pages.
If pAllocator
is not NULL, pAllocatormust be a valid pointer to a valid
AllocationCallbacks structure
functionmust have
been created, allocated, or retrieved from device
There is currently no specification language written for this command.
This section acts only as placeholder and to avoid dead links in the
specification and reference pages.
There is currently no specification language written for this type. This
section acts only as placeholder and to avoid dead links in the
specification and reference pages.
The sType value of
each structure in the pNext chain must be unique
If dataSize is not
0, pDatamust be a valid pointer to an array of dataSize
bytes
There is currently no specification language written for this type. This
section acts only as placeholder and to avoid dead links in the
specification and reference pages.
There is currently no specification language written for this command.
This section acts only as placeholder and to avoid dead links in the
specification and reference pages.
If pAllocator is
not NULL, pAllocatormust be a valid pointer to a valid
AllocationCallbacks structure
modulemust have been
created, allocated, or retrieved from device
There is currently no specification language written for this command.
This section acts only as placeholder and to avoid dead links in the
specification and reference pages.
There is currently no specification language written for this type. This
section acts only as placeholder and to avoid dead links in the
specification and reference pages.
To ensure that destroyCuModuleNVX is always called: pass
bracket (or the allocate function from your
favourite resource management library) as the last argument.
To just extract the pair pass (,) as the last argument.
To ensure that destroyCuFunctionNVX is always called: pass
bracket (or the allocate function from your
favourite resource management library) as the last argument.
To just extract the pair pass (,) as the last argument.
The primary expected use of ERROR_VALIDATION_FAILED_EXT is for
validation layer testing to prevent invalid commands from reaching the
ICD. It is not expected that an application would see this error code
during normal use of the validation layers. If an application returns
TRUE in
DebugUtilsMessengerCallbackDataEXT,
the validation layers will return this error code instead of passing the
command down the dispatch chain.