nvitop.libcuda module
Python bindings for the CUDA Driver APIs.
- nvitop.libcuda.CUDA_SUCCESS = 0
The API call returned with no errors. In the case of query calls, this also means that the operation being queried is complete (see
cuEventQuery()
andcuStreamQuery()
).
- nvitop.libcuda.CUDA_ERROR_INVALID_VALUE = 1
This indicates that one or more of the parameters passed to the API call is not within an acceptable range of values.
- nvitop.libcuda.CUDA_ERROR_OUT_OF_MEMORY = 2
The API call failed because it was unable to allocate enough memory to perform the requested operation.
- nvitop.libcuda.CUDA_ERROR_NOT_INITIALIZED = 3
This indicates that the CUDA driver has not been initialized with
cuInit()
or that initialization has failed.
- nvitop.libcuda.CUDA_ERROR_DEINITIALIZED = 4
This indicates that the CUDA driver is in the process of shutting down.
- nvitop.libcuda.CUDA_ERROR_PROFILER_DISABLED = 5
This indicates profiler is not initialized for this run. This can happen when the application is running with external profiling tools like visual profiler.
- nvitop.libcuda.CUDA_ERROR_STUB_LIBRARY = 34
This indicates that the CUDA driver that the application has loaded is a stub library. Applications that run with the stub rather than a real driver loaded will result in CUDA API returning this error.
- nvitop.libcuda.CUDA_ERROR_DEVICE_UNAVAILABLE = 46
This indicates that requested CUDA device is unavailable at the current time. Devices are often unavailable due to use of
CU_COMPUTEMODE_EXCLUSIVE_PROCESS
orCU_COMPUTEMODE_PROHIBITED
.
- nvitop.libcuda.CUDA_ERROR_NO_DEVICE = 100
This indicates that no CUDA - capable devices were detected by the installed CUDA driver.
- nvitop.libcuda.CUDA_ERROR_INVALID_DEVICE = 101
This indicates that the device ordinal supplied by the user does not correspond to a valid CUDA device or that the action requested is invalid for the specified device.
- nvitop.libcuda.CUDA_ERROR_DEVICE_NOT_LICENSED = 102
This error indicates that the Grid license is not applied.
- nvitop.libcuda.CUDA_ERROR_INVALID_IMAGE = 200
This indicates that the device kernel image is invalid. This can also indicate an invalid CUDA module.
- nvitop.libcuda.CUDA_ERROR_INVALID_CONTEXT = 201
This most frequently indicates that there is no context bound to the current thread. This can also be returned if the context passed to an API call is not a valid handle (such as a context that has had
cuCtxDestroy()
invoked on it). This can also be returned if a user mixes different API versions (i.e. 3010 context with 3020 API calls). SeecuCtxGetApiVersion()
for more details.
- nvitop.libcuda.CUDA_ERROR_MAP_FAILED = 205
This indicates that a map or register operation has failed.
- nvitop.libcuda.CUDA_ERROR_UNMAP_FAILED = 206
This indicates that an unmap or unregister operation has failed.
- nvitop.libcuda.CUDA_ERROR_ARRAY_IS_MAPPED = 207
This indicates that the specified array is currently mapped and thus cannot be destroyed.
- nvitop.libcuda.CUDA_ERROR_ALREADY_MAPPED = 208
This indicates that the resource is already mapped.
- nvitop.libcuda.CUDA_ERROR_NO_BINARY_FOR_GPU = 209
This indicates that there is no kernel image available that is suitable for the device. This can occur when a user specifies code generation options for a particular CUDA source file that do not include the corresponding device configuration.
- nvitop.libcuda.CUDA_ERROR_ALREADY_ACQUIRED = 210
This indicates that a resource has already been acquired.
- nvitop.libcuda.CUDA_ERROR_NOT_MAPPED = 211
This indicates that a resource is not mapped.
- nvitop.libcuda.CUDA_ERROR_NOT_MAPPED_AS_ARRAY = 212
This indicates that a mapped resource is not available for access as an array.
- nvitop.libcuda.CUDA_ERROR_NOT_MAPPED_AS_POINTER = 213
This indicates that a mapped resource is not available for access as a pointer.
- nvitop.libcuda.CUDA_ERROR_ECC_UNCORRECTABLE = 214
This indicates that an uncorrectable ECC error was detected during execution.
- nvitop.libcuda.CUDA_ERROR_UNSUPPORTED_LIMIT = 215
This indicates that the
CUlimit
passed to the API call is not supported by the active device.
- nvitop.libcuda.CUDA_ERROR_CONTEXT_ALREADY_IN_USE = 216
This indicates that the
CUcontext
passed to the API call can only be bound to a single CPU thread at a time but is already bound to a CPU thread.
- nvitop.libcuda.CUDA_ERROR_PEER_ACCESS_UNSUPPORTED = 217
This indicates that peer access is not supported across the given devices.
- nvitop.libcuda.CUDA_ERROR_INVALID_PTX = 218
This indicates that a PTX JIT compilation failed.
- nvitop.libcuda.CUDA_ERROR_INVALID_GRAPHICS_CONTEXT = 219
This indicates an error with OpenGL or DirectX context.
- nvitop.libcuda.CUDA_ERROR_NVLINK_UNCORRECTABLE = 220
This indicates that an uncorrectable NVLink error was detected during the execution.
- nvitop.libcuda.CUDA_ERROR_JIT_COMPILER_NOT_FOUND = 221
This indicates that the PTX JIT compiler library was not found.
- nvitop.libcuda.CUDA_ERROR_UNSUPPORTED_PTX_VERSION = 222
This indicates that the provided PTX was compiled with an unsupported toolchain.
- nvitop.libcuda.CUDA_ERROR_JIT_COMPILATION_DISABLED = 223
This indicates that the PTX JIT compilation was disabled.
- nvitop.libcuda.CUDA_ERROR_UNSUPPORTED_EXEC_AFFINITY = 224
This indicates that the
CUexecAffinityType
passed to the API call is not supported by the active device.
- nvitop.libcuda.CUDA_ERROR_INVALID_SOURCE = 300
This indicates that the device kernel source is invalid. This includes compilation / linker errors encountered in device code or user error.
- nvitop.libcuda.CUDA_ERROR_FILE_NOT_FOUND = 301
This indicates that the file specified was not found.
- nvitop.libcuda.CUDA_ERROR_SHARED_OBJECT_SYMBOL_NOT_FOUND = 302
This indicates that a link to a shared object failed to resolve.
- nvitop.libcuda.CUDA_ERROR_SHARED_OBJECT_INIT_FAILED = 303
This indicates that initialization of a shared object failed.
- nvitop.libcuda.CUDA_ERROR_OPERATING_SYSTEM = 304
This indicates that an OS call failed.
- nvitop.libcuda.CUDA_ERROR_INVALID_HANDLE = 400
This indicates that a resource handle passed to the API call was not valid. Resource handles are opaque types like
CUstream
andCUevent
.
- nvitop.libcuda.CUDA_ERROR_ILLEGAL_STATE = 401
This indicates that a resource required by the API call is not in a valid state to perform the requested operation.
- nvitop.libcuda.CUDA_ERROR_NOT_FOUND = 500
This indicates that a named symbol was not found. Examples of symbols are global / constant variable names, driver function names, texture names, and surface names.
- nvitop.libcuda.CUDA_ERROR_NOT_READY = 600
This indicates that asynchronous operations issued previously have not completed yet. This result is not actually an error, but must be indicated differently than
CUDA_SUCCESS
(which indicates completion). Calls that may return this value includecuEventQuery()
andcuStreamQuery()
.
- nvitop.libcuda.CUDA_ERROR_ILLEGAL_ADDRESS = 700
While executing a kernel, the device encountered a load or store instruction on an invalid memory address. This leaves the process in an inconsistent state and any further CUDA work will return the same error. To continue using CUDA, the process must be terminated and relaunched.
- nvitop.libcuda.CUDA_ERROR_LAUNCH_OUT_OF_RESOURCES = 701
This indicates that a launch did not occur because it did not have appropriate resources. This error usually indicates that the user has attempted to pass too many arguments to the device kernel, or the kernel launch specifies too many threads for the kernel’s register count. Passing arguments of the wrong size (i.e. a 64 - bit pointer when a 32 - bit int is expected) is equivalent to passing too many arguments and can also result in this error.
- nvitop.libcuda.CUDA_ERROR_LAUNCH_TIMEOUT = 702
This indicates that the device kernel took too long to execute. This can only occur if timeouts are enabled - see the device attribute
CU_DEVICE_ATTRIBUTE_KERNEL_EXEC_TIMEOUT
for more information. This leaves the process in an inconsistent state and any further CUDA work will return the same error. To continue using CUDA, the process must be terminated and relaunched.
- nvitop.libcuda.CUDA_ERROR_LAUNCH_INCOMPATIBLE_TEXTURING = 703
This error indicates a kernel launch that uses an incompatible texturing mode.
- nvitop.libcuda.CUDA_ERROR_PEER_ACCESS_ALREADY_ENABLED = 704
This error indicates that a call to
cuCtxEnablePeerAccess()
is trying to re - enable peer access to a context which has already had peer access to it enabled.
- nvitop.libcuda.CUDA_ERROR_PEER_ACCESS_NOT_ENABLED = 705
This error indicates that
cuCtxDisablePeerAccess()
is trying to disable peer access which has not been enabled yet viacuCtxEnablePeerAccess()
.
- nvitop.libcuda.CUDA_ERROR_PRIMARY_CONTEXT_ACTIVE = 708
This error indicates that the primary context for the specified device has already been initialized.
- nvitop.libcuda.CUDA_ERROR_CONTEXT_IS_DESTROYED = 709
This error indicates that the context current to the calling thread has been destroyed using
cuCtxDestroy()
, or is a primary context which has not yet been initialized.
- nvitop.libcuda.CUDA_ERROR_ASSERT = 710
A device - side assert triggered during kernel execution. The context cannot be used anymore, and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed if the program is to continue using CUDA.
- nvitop.libcuda.CUDA_ERROR_TOO_MANY_PEERS = 711
This error indicates that the hardware resources required to enable peer access have been exhausted for one or more of the devices passed to
cuCtxEnablePeerAccess()
.
- nvitop.libcuda.CUDA_ERROR_HOST_MEMORY_ALREADY_REGISTERED = 712
This error indicates that the memory range passed to
cuMemHostRegister()
has already been registered.
- nvitop.libcuda.CUDA_ERROR_HOST_MEMORY_NOT_REGISTERED = 713
This error indicates that the pointer passed to
cuMemHostUnregister()
does not correspond to any currently registered memory region.
- nvitop.libcuda.CUDA_ERROR_HARDWARE_STACK_ERROR = 714
While executing a kernel, the device encountered a stack error. This can be due to stack corruption or exceeding the stack size limit. This leaves the process in an inconsistent state and any further CUDA work will return the same error. To continue using CUDA, the process must be terminated and relaunched.
- nvitop.libcuda.CUDA_ERROR_ILLEGAL_INSTRUCTION = 715
While executing a kernel, the device encountered an illegal instruction. This leaves the process in an inconsistent state and any further CUDA work will return the same error. To continue using CUDA, the process must be terminated and relaunched.
- nvitop.libcuda.CUDA_ERROR_MISALIGNED_ADDRESS = 716
While executing a kernel, the device encountered a load or store instruction on a memory address which is not aligned. This leaves the process in an inconsistent state and any further CUDA work will return the same error. To continue using CUDA, the process must be terminated and relaunched.
- nvitop.libcuda.CUDA_ERROR_INVALID_ADDRESS_SPACE = 717
While executing a kernel, the device encountered an instruction which can only operate on memory locations in certain address spaces (global, shared, or local), but was supplied a memory address not belonging to an allowed address space. This leaves the process in an inconsistent state and any further CUDA work will return the same error. To continue using CUDA, the process must be terminated and relaunched.
- nvitop.libcuda.CUDA_ERROR_INVALID_PC = 718
While executing a kernel, the device program counter wrapped its address space. This leaves the process in an inconsistent state and any further CUDA work will return the same error. To continue using CUDA, the process must be terminated and relaunched.
- nvitop.libcuda.CUDA_ERROR_LAUNCH_FAILED = 719
An exception occurred on the device while executing a kernel. Common causes include dereferencing an invalid device pointer and accessing out of bounds shared memory. Less common cases can be system specific - more information about these cases can be found in the system specific user guide. This leaves the process in an inconsistent state and any further CUDA work will return the same error. To continue using CUDA, the process must be terminated and relaunched.
- nvitop.libcuda.CUDA_ERROR_COOPERATIVE_LAUNCH_TOO_LARGE = 720
This error indicates that the number of blocks launched per grid for a kernel that was launched via either
cuLaunchCooperativeKernel()
orcuLaunchCooperativeKernelMultiDevice()
exceeds the maximum number of blocks as allowed bycuOccupancyMaxActiveBlocksPerMultiprocessor()
orcuOccupancyMaxActiveBlocksPerMultiprocessorWithFlags()
times the number of multiprocessors as specified by the device attributeCU_DEVICE_ATTRIBUTE_MULTIPROCESSOR_COUNT
.
- nvitop.libcuda.CUDA_ERROR_NOT_PERMITTED = 800
This error indicates that the attempted operation is not permitted.
- nvitop.libcuda.CUDA_ERROR_NOT_SUPPORTED = 801
This error indicates that the attempted operation is not supported on the current system or device.
- nvitop.libcuda.CUDA_ERROR_SYSTEM_NOT_READY = 802
This error indicates that the system is not yet ready to start any CUDA work. To continue using CUDA, verify the system configuration is in a valid state and all required driver daemons are actively running. More information about this error can be found in the system specific user guide.
- nvitop.libcuda.CUDA_ERROR_SYSTEM_DRIVER_MISMATCH = 803
This error indicates that there is a mismatch between the versions of the display driver and the CUDA driver. Refer to the compatibility documentation for supported versions.
- nvitop.libcuda.CUDA_ERROR_COMPAT_NOT_SUPPORTED_ON_DEVICE = 804
This error indicates that the system was upgraded to run with forward compatibility but the visible hardware detected by CUDA does not support this configuration. Refer to the compatibility documentation for the supported hardware matrix or ensure that only supported hardware is visible during initialization via the
CUDA_VISIBLE_DEVICES
environment variable.
- nvitop.libcuda.CUDA_ERROR_MPS_CONNECTION_FAILED = 805
This error indicates that the MPS client failed to connect to the MPS control daemon or the MPS server.
- nvitop.libcuda.CUDA_ERROR_MPS_RPC_FAILURE = 806
This error indicates that the remote procedural call between the MPS server and the MPS client failed.
- nvitop.libcuda.CUDA_ERROR_MPS_SERVER_NOT_READY = 807
This error indicates that the MPS server is not ready to accept new MPS client requests. This error can be returned when the MPS server is in the process of recovering from a fatal failure.
- nvitop.libcuda.CUDA_ERROR_MPS_MAX_CLIENTS_REACHED = 808
This error indicates that the hardware resources required to create MPS client have been exhausted.
- nvitop.libcuda.CUDA_ERROR_MPS_MAX_CONNECTIONS_REACHED = 809
This error indicates the the hardware resources required to support device connections have been exhausted.
- nvitop.libcuda.CUDA_ERROR_STREAM_CAPTURE_UNSUPPORTED = 900
This error indicates that the operation is not permitted when the stream is capturing.
- nvitop.libcuda.CUDA_ERROR_STREAM_CAPTURE_INVALIDATED = 901
This error indicates that the current capture sequence on the stream has been invalidated due to a previous error.
- nvitop.libcuda.CUDA_ERROR_STREAM_CAPTURE_MERGE = 902
This error indicates that the operation would have resulted in a merge of two independent capture sequences.
- nvitop.libcuda.CUDA_ERROR_STREAM_CAPTURE_UNMATCHED = 903
This error indicates that the capture was initiated not in this stream.
- nvitop.libcuda.CUDA_ERROR_STREAM_CAPTURE_UNJOINED = 904
This error indicates that the capture sequence contains a fork that was not joined to the primary stream.
- nvitop.libcuda.CUDA_ERROR_STREAM_CAPTURE_ISOLATION = 905
This error indicates that a dependency would have been created which crosses the capture sequence boundary. Only implicit in -stream ordering dependencies are allowed to cross the boundary.
- nvitop.libcuda.CUDA_ERROR_STREAM_CAPTURE_IMPLICIT = 906
This error indicates a disallowed implicit dependency on a current capture sequence from
cudaStreamLegacy()
.
- nvitop.libcuda.CUDA_ERROR_CAPTURED_EVENT = 907
This error indicates that the operation is not permitted on an event which was last recorded in a capturing stream.
- nvitop.libcuda.CUDA_ERROR_STREAM_CAPTURE_WRONG_THREAD = 908
A stream capture sequence not initiated with the
CU_STREAM_CAPTURE_MODE_RELAXED
argument tocuStreamBeginCapture()
was passed tocuStreamEndCapture()
in a different thread.
- nvitop.libcuda.CUDA_ERROR_TIMEOUT = 909
This error indicates that the timeout specified for the wait operation has lapsed.
- nvitop.libcuda.CUDA_ERROR_GRAPH_EXEC_UPDATE_FAILURE = 910
This error indicates that the graph update was not performed because it included changes which violated constraints specific to instantiated graph update.
- nvitop.libcuda.CUDA_ERROR_EXTERNAL_DEVICE = 911
This indicates that an async error has occurred in a device outside of CUDA. If CUDA was waiting for an external device’s signal before consuming shared data, the external device signaled an error indicating that the data is not valid for consumption. This leaves the process in an inconsistent state and any further CUDA work will return the same error. To continue using CUDA, the process must be terminated and relaunched.
- nvitop.libcuda.CUDA_ERROR_UNKNOWN = 999
This indicates that an unknown internal error has occurred.