oneAPI Level Zero

This repository contains the following components of oneAPI:

• Copies of the Level Zero Specification API C/C++ header files
• Level Zero Loader
• Level Zero Validation Layer
• Level Zero Tracing Layer

This project is part of the larger oneAPI project.

See the oneAPI specification for more information about the oneAPI project.

See the Level Zero specification for more information about Level Zero.

See the Level Zero specification repo for contributing to the specification.

Level Zero API versions are listed in the ze_api_version_t enumeration, located in the ze_api.h file.

Building and Installing

Project is defined using CMake.

Linux

mkdir build
cd build
cmake .. -D CMAKE_BUILD_TYPE=Release
cmake --build . --target package
cmake --build . --target install

Static Loader

To build the Loader statically one must set -DBUILD_STATIC=1 during the cmake configuration step.

The build of the static loader creates a ze_loader.a/.lib which will link the source/lib source code into your application or library.

This enables for inclusion of all L0 symbols into your application/library allowing for backwards compatability with older versions of the Loader.

The static loader "shim" dynamically loads the ze_loader.so/.dll on the system enabling plugin like behavior where the init will fail gracefully given a usable loader or L0 driver is not found.

When the -DBUILD_STATIC=1 is executed, the dynamic loader and layers are not built to avoid conflicts during local test execution which requires the dynamic loader and layers to all be the same version for compatability.

Testing with the static loader requires a build of the dynamic loader or an installation of the dynamic loader to exist in the library path.

Debug Trace

The Level Zero Loader has the ability to print warnings and errors which occur within the internals of the Level Zero Loader itself.

To enable this debug tracing feature, set the environment variable ZE_ENABLE_LOADER_DEBUG_TRACE=1.

This will enforce the Loader to print all errors whether fatal or non-fatal to stderr with the PREFIX ZE_LOADER_DEBUG_TRACE:.

Logging to File - PREVIEW

The Level Zero Loader uses spdlog logging and can be controlled via environment variables:

ZEL_ENABLE_LOADER_LOGGING=1

[DEPRECATED] ZEL_LOADER_LOG_FILE=/path/to/logfile

ZEL_LOADER_LOG_DIR='/directory/path'

ZEL_LOADER_LOGGING_LEVEL=debug

Valid logging levels are trace, debug, info, warn, error, critical, off. Logging is disabled by default but when enabled the default level is 'warn'. The default log file is 'ze_loader.log' in '.oneapi_logs' in the current user's home directory.

This feature is in early development and is preview only.

Logging API calls

The Level Zero Loader will log all API calls whenever logging level is set to trace and validation layer is enabled. Following variables need to be set to enable API logging:

ZEL_ENABLE_LOADER_LOGGING=1

ZEL_LOADER_LOGGING_LEVEL=trace

ZE_ENABLE_VALIDATION_LAYER=1

By default logs will be written to the log file, as described above. To print the logs to stderr instead, ZEL_LOADER_LOG_CONSOLE=1 needs to be set.

Driver/Device Sorting

As of v1.20.3 of the Loader, Drivers and Devices reported to the user are sorted to enable the first device to be the best available device.

• By default, drivers will be sorted such that the ordering will be:
  • Drivers with Discrete GPUs only
  • Drivers with Discrete and Integrated GPUs
  • Drivers with Integrated GPUs
  • Drivers with Mixed Devices Types (ie GPU + NPU)
  • Drivers with Non GPU Devices Only
• If ZE_ENABLE_PCI_ID_DEVICE_ORDER is set, then the following ordering is provided:
  • Drivers with Integrated GPUs
  • Drivers with Discrete and Integrated GPUs
  • Drivers with Discrete GPUs only
  • Drivers with Mixed Devices Types (ie GPU + NPU)
  • Drivers with Non GPU Devices Only

The order of the sorting is based on the enumerator: zel_driver_type_t

The ordering of the drivers reported to the user is based on the order of the enumerations provided. When additional driver types are added, they should be added to the end of the list to avoid reporting new device types before known device types.

Contributing

See CONTRIBUTING for more information.

License

Distributed under the MIT license. See LICENSE for more information.

Security

See Intel's Security Center for information on how to report a potential security issue or vulnerability.

See also SECURITY.