Intel® Graphics Compute Runtime for oneAPI Level Zero and OpenCL™ Driver
Go to file
Mateusz Jablonski 2a60522e6e refactor l0 api: cleanup cmake files
Related-To: NEO-7507
Signed-off-by: Mateusz Jablonski <mateusz.jablonski@intel.com>
2023-03-17 09:58:52 +01:00
.github ci: exclude third_party in actions/neo-lint 2023-01-27 10:45:31 +01:00
cmake refactor(cmake): check images support per platform instead of per core 2023-03-13 16:14:39 +01:00
level_zero refactor l0 api: cleanup cmake files 2023-03-17 09:58:52 +01:00
manifests ci: infra update 2023-03-16 10:35:29 +01:00
opencl Introduce Online, Offline, Disabled DebuggingModes 2023-03-17 09:31:17 +01:00
programmers-guide Updated Programmer's Guide with details on Symbols in L0 Modules 2023-02-16 10:50:24 +01:00
scripts build: update package architecture for intel-level-zero-gpu* 2023-03-03 13:27:10 +01:00
shared Introduce Online, Offline, Disabled DebuggingModes 2023-03-17 09:31:17 +01:00
target_aub_tests Update aubstream interface: use product family from aubstream 2022-11-21 15:30:09 +01:00
target_unit_tests feature: Add support for MTL 2022-12-23 10:22:50 +01:00
third_party feature: add experimental support for cl-gl sharing on Linux 2023-03-17 08:58:29 +01:00
.branch
.clang-format Remove test.h from .clang-format file 2021-12-15 16:22:38 +01:00
.clang-tidy Disable unnecessary clang-tidy checks 2022-06-28 16:56:56 +02:00
.ctags
.gitattributes
.gitignore Add VS Code output directory to .gitignore 2022-06-21 18:08:05 +02:00
.lint-revision ci: lint revision update 2023-02-21 15:18:18 +01:00
BUILD.md cleanup info about external repositories/projects 2022-03-03 14:51:47 +01:00
CMakeLists.txt refactor(cmake): check images support per platform instead of per core 2023-03-13 16:14:39 +01:00
CONTRIBUTING.md Add copyright headers to markdown files 2021-06-28 16:31:27 +02:00
FAQ.md Documentation: Clarify distro support. 2022-11-02 13:42:53 +01:00
GUIDELINES.md Add rules for defining global constant variables to GUIDELINES.md 2022-08-29 14:45:18 +02:00
Jenkinsfile dependencies update 2023-03-09 17:35:07 +01:00
LICENSE.md Use full license text in LICENSE.md 2022-10-12 14:36:12 +02:00
README.md Documentation: Release cadence update 2022-11-30 12:58:29 +01:00
WSL.md WSL - updating instructions 2021-11-09 20:15:23 +01:00
config.h.in Copyright header update 2021-05-17 20:38:19 +02:00
driver_version.h.in Add interface to extract versioning info 2021-06-29 13:17:15 +02:00
hw_cmds_default.h.in hw_cmds.h usage refactor 2022-06-29 18:03:21 +02:00
igc.opencl.h.in
lib_names.h.in
os_release_info.cmake
package.cmake CMake cleanup: move opencl logic to opencl folder 2021-11-12 12:23:45 +01:00
package_config.cmake
platforms.cmake refactor(cmake): check images support per platform instead of per core 2023-03-13 16:14:39 +01:00
test_files_setup.h.in use test_files from source location in ults 2022-05-20 14:20:13 +02:00
ubsan.supp
version.cmake Release support for L0 v1.3 2022-01-24 15:12:33 +01:00

README.md

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:

Dependencies

In addition, to enable performance counters support, the following packages are needed:

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

OpenCL specific

(*) Other names and brands may be claimed as property of others.