Awesome
<!--- Copyright (C) 2018-2023 Intel Corporation SPDX-License-Identifier: MIT -->Intel(R) Graphics Compute Runtime for oneAPI Level Zero and OpenCL(TM) Driver
Introduction
The Intel(R) Graphics Compute Runtime for oneAPI Level Zero and OpenCL(TM) Driver is an open source project providing compute API support (Level Zero, OpenCL) for Intel graphics hardware architectures (HD Graphics, Xe).
What is NEO?
NEO is the shorthand name for Compute Runtime contained within this repository. It is also a development mindset that we adopted when we first started the implementation effort for OpenCL.
The project evolved beyond a single API and NEO no longer implies a specific API. When talking about a specific API, we will mention it by name (e.g. Level Zero, OpenCL).
License
The Intel(R) Graphics Compute Runtime for oneAPI Level Zero and OpenCL(TM) Driver is distributed under the MIT License.
You may obtain a copy of the License at: https://opensource.org/licenses/MIT
Supported Platforms
Platform | OpenCL | Level Zero |
---|---|---|
Intel Core Processors with Gen8 graphics devices (formerly Broadwell) | 3.0 | - |
Intel Core Processors with Gen9 graphics devices (formerly Skylake, Kaby Lake, Coffee Lake) | 3.0 | Y |
Intel Atom Processors with Gen9 graphics devices (formerly Apollo Lake, Gemini Lake) | 3.0 | - |
Intel Core Processors with Gen11 graphics devices (formerly Ice Lake) | 3.0 | Y |
Intel Atom Processors with Gen11 graphics devices (formerly Elkhart Lake) | 3.0 | - |
Intel Core Processors with Gen12 graphics devices (formerly Tiger Lake, Rocket Lake, Alder Lake) | 3.0 | Y |
Release cadence
Release cadence changed from weekly to monthly late 2022
- At the beginning of each calendar month, we identify a well-tested driver version from the previous month as a release candidate for our monthly release.
- We create a release branch and apply selected fixes for significant issues.
- The branch naming convention is releases/yy.ww (yy - year, ww - work week of release candidate)
- The builds are tagged using the following format: yy.ww.bbbbb.hh (yy - year, ww - work week, bbbbb - incremental build number from the master branch, hh - incremental commit number on release branch).
- We publish and document a monthly release from the tip of that branch.
- During subsequent weeks of a given month, we continue to cherry-pick fixes to that branch and may publish a hotfix release.
- Quality level of the driver (per platform) will be provided in the Release Notes.
Installation Options
To allow NEO access to GPU device make sure user has permissions to files /dev/dri/renderD*.
Via system package manager
NEO is available for installation on a variety of Linux distributions and can be installed via the distro's package manager.
For example on Ubuntu* 22.04:
apt-get install intel-opencl-icd
Manual download
.deb packages for Ubuntu are provided along with installation instructions and Release Notes on the release page
Linking applications
Directly linking to the runtime library is not supported:
- Level Zero applications should link with Level Zero loader
- OpenCL applications should link with ICD loader library (ocl-icd)
Dependencies
- GmmLib - https://github.com/intel/gmmlib
- Intel Graphics Compiler - https://github.com/intel/intel-graphics-compiler
In addition, to enable performance counters support, the following packages are needed:
- Intel(R) Metrics Discovery (MDAPI) - https://github.com/intel/metrics-discovery
- Intel(R) Metrics Library for MDAPI - https://github.com/intel/metrics-library
How to provide feedback
By default, please submit an issue using native github.com interface.
How to contribute
Create a pull request on github.com with your patch. Make sure your change is cleanly building and passing ULTs. A maintainer will contact you if there are questions or concerns. See contribution guidelines for more details.
See also
Level Zero specific
- oneAPI Level Zero specification
- Intel(R) OneApi Level Zero Specification API C/C++ header files
- oneAPI Level Zero tests
OpenCL specific
- OpenCL on Linux guide
- Intel(R) GPU Compute Samples
- Frequently Asked Questions
- Interoperability with VTune
- OpenCL Conformance Tests
(*) Other names and brands may be claimed as property of others.