clinfo [options ...]
clinfo prints all available information about all OpenCL platforms available on the system and the devices they expose.
clinfo accepts the following options:
- -a, --all-props
try to retrieve all properties, even those not officially supported (e.g. because they require specific extensions), but only show them if the property could be retrieved successfully; see also the Limitations section below; note that even though this may reveal hidden properties, there is no guarantee that the returned values are meaningful, nor that the corresponding feature is actually available at all;
- -A, --always-all-props
like -a, but also show errors;
produce human-friendly output; this is the default (except as noted below);
produce machine-friendly output; this is the default if clinfo is invoked with a name that contains the string “raw”;
shows also offline devices for platforms that expose this feature;
- -l, --list
list platforms and devices by name, with no (other) properties;
- -h, -?
- --version, -v
show program version.
OpenCL 1.1, OpenCL 1.2, OpenCL 2.0, OpenCL 2.1, OpenCL 2.2.
Supported OpenCL extensions:
- cl_khr_fp16, cl_khr_fp64, cl_amd_fp64, cl_APPLE_fp64_basic_ops
for information about support for half-precision and double-precision floating-point data types;
for information about the base address and pitch alignment requirements of buffers to be used as base for 2D images;
for information about the supported IL (Intermediate Language) representations;
for information about the supported SPIR (Standard Portable Intermediate Representation) versions;
for the suffix of vendor extensions functions;
for the maximum number of named sub-group barriers;
for the terminate capabilities for the device;
for device fission support in OpenCL 1.1 devices;
for the atomic counter extension;
for AMD-specific device attributes;
to show the maximum number of keys supported by the platform;
to show offline devices exposed by the platform, if requested (see --offline option);
to show the number and IDs of available P2P devices;
for Shared Virtual Memory (SVM) capabilities in OpenCL 1.2 devices;
for NVIDIA-specific device attributes;
for the Intel extension allowing CPU devices to run kernels as part of the current host thread;
for the version of the Intel Motion Estimation accelerator version;
for the version and supported features of Intel's device-side AVC Motion;
for the maximum dimensions of planar YUV images;
for simultaneous CL/GL/DirectX context sharing (only partial support);
to enumerate allowed sub-group sizes;
for the Altera extension to query the core temperature of the device;
for the QUALCOMM extension to query page size and required padding in external memory allocation.
Some information is duplicated when available from multiple sources. Examples:
- supported device partition types and domains as obtained using the cl_ext_device_fission extension typically match the ones obtained using the core OpenCL 1.2 device partition feature;
- the preferred work-group size multiple matches the NVIDIA warp size (on NVIDIA devices) or the AMD wavefront width (on AMD devices).
Some floating-point configuration flags may only be meaningful for specific precisions and/or specific OpenCL versions. For example, CL_FP_CORRECTLY_ROUNDED_DIVIDE_SQRT is only relevant for single precision in OpenCL 1.2 devices.
The implementation-defined behavior for NULL platform or context properties is tested for the following API calls:
by trying to show the platform name;
by trying to enumerate devices; the corresponding platform (if any) is then detected by querying the device platform of the first device;
by trying to create a context from a device from the previous list (if any), and a context from a device from a different platform;
by trying to create contexts for each device type (except DEFAULT).
Support for OpenCL 2.x properties is not fully tested.
Support for cl_khr_subgroup_named_barrier is experimental due to missing definitions in the official OpenCL headers.
Raw (machine-parsable) output is considered experimental, the output format might still undergo changes.
The properties of the ICD loader will also be queried if the clGetICDLoaderInfoOCLICD extension function is found.
Support for the properties exposed by cl_amd_copy_buffer_p2p is experimental.
Support for some (documented and undocumented) properties exposed by cl_amd_device_attribute_query is experimental (see also Limitations).
Support for the interop lists exposed by cl_intel_simultaneous_sharing is experimental.
The highest OpenCL version supported by the ICD loader is detected with some trivial heuristics (symbols found); a notice is output if this is lower than the highest platform OpenCL version, or if the detected version doesn't match the one declared by the ICD loader itself.
OpenCL provides no explicit mean to detect the supported version of any extension exposed by a device, which makes it impossible to determine a priori if it will be possible to successfully query a device about a specific property. Additionally, the actual size and meaning of some properties are not officially declared anywhere.
Most notably, this affects extensions such as cl_amd_device_attribute_query and cl_nv_device_attribute_query. Heuristics based on standard version support are partially used in the code to determine which version may be supported.
Properties which are known to be affected by these limitations include:
documented in v3 of the cl_amd_device_attribute_query extension specification as being the global free memory in KBytes, without any explanation given on why there are two values;
documented in v3 of the cl_amd_device_attribute_query extension specification, but not reported by drivers supporting other v3 properties. This has now been enabled for drivers assumed to support v4 of the same extension;
exposed by the cl_khr_terminate_context has changed value between OpenCL 1.x and 2.x, and it's allegedly a bitfield, whose values are however not defined anywhere.
Please report any issues on the project tracker on GitHub.