oneapi-src · nrspruit · Jan 10, 2025 · Jan 10, 2025 · Jan 10, 2025
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,7 +1,15 @@
 # Level zero loader changelog
 
+## v1.20.1
+* Update to spec 1.12.15
+* Update Docs for spec links and corrections
 ## v1.20.0
 * Update to spec 1.12
+* Allow pkg-config files on Windows as well
+* Fix GET_FUNCTION_PTR warnings on windows
+* Fix libddi table query code generation
+* Fixed pkg-config files generation
+* fixed potential memory leaks in events checker
 ## v1.19.2
 * Remove static result in InitDrivers given first init fails
 ## v1.19.1

diff --git a/CMakeLists.txt b/CMakeLists.txt
@@ -13,7 +13,7 @@ if(MSVC AND (MSVC_VERSION LESS 1900))
 endif()
 
 # This project follows semantic versioning (https://semver.org/)
-project(level-zero VERSION 1.20.0)
+project(level-zero VERSION 1.20.1)
 
 include(GNUInstallDirs)
 

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -20,7 +20,7 @@ review these for proper alignment with the
 
 * The functionality in the Level Zero Loader and layers which follow the Level Zero spec must follow these naming conventions:
 
-  * https://spec.oneapi.io/level-zero/latest/core/INTRO.html#naming-convention
+  * https://oneapi-src.github.io/level-zero-spec/level-zero/latest/core/INTRO.html#naming-convention
 
 * If the contributions are adding new functionality unique to the Level Zero Loader (ie not Level Zero Spec related):
   * Level Zero Loader specific APIs must have the prefix: `zel`
@@ -36,12 +36,14 @@ To generate the code from the scripts, run the following commands:
 * Clone the specification repo: `git clone https://github.com/oneapi-src/level-zero-spec.git level-zero-spec`
 * Checkout the specification version in the specification repo, for example:
   * `cd level-zero-spec`
-  * `git checkout v1.5`
-* Generate the specification JSON file:
-  * `cd ./scripts`
-  * `python3 ./run.py --debug '--!html' '--!rst' '--!build' --ver 1.5`
+  * `git checkout v1.12.15`
+* Generate the specification JSON file and Headers:
+  * `cd level-zero-spec/scripts`
+  * `python3 ./run.py --debug '--!html' '--!rst' '--!build' --ver 1.12`
+* Copy the Headers From Spec to Loader repo
+  * `cp level-zero-spec/include/* level-zero/include/`
 * Execute the json2src script in the level-zero repo with the input.json in the specification repo with the corresponding spec version, for example:
-  * `./scripts/json2src.py --ver 1.5 --api-json <path to level-zero-spec checkout>/scripts/input.json .`
+  * `./level-zero/scripts/json2src.py --ver 1.12 --api-json level-zero-spec/scripts/input.json .`
 
 These scripts update the code with what would be generated in the next specification update.
 
@@ -56,7 +58,7 @@ When performing a code review please refer to this checklist to guide your comme
 
 * Does the code follow C++ Coding Standards? [C++ Coding Standards](#c-coding-standards).
 * Does the code follow the Level Zero naming conventions? [Naming Conventions](#naming-conventions).
-* Does the code follow the Level Zero specification? See here for the latest spec: https://spec.oneapi.io/level-zero/latest/index.html.
+* Does the code follow the Level Zero specification? See here for the latest spec: https://oneapi-src.github.io/level-zero-spec/level-zero/latest/index.html.
 * Is the code for the Validation Layer? Please review the following: [Validation Layer README](source/layers/validation/README.md).
 * Is the code for the Tracing Layer? Please review the following: [Tracing Layer README](source/layers/tracing/README.md).
 * Is the code "Vendor & Platform agnostic"? ie Are the changes in the loader or in the layers ignorant of the implementation in the L0 drivers?

diff --git a/include/ze.py b/include/ze.py
@@ -4,7 +4,7 @@
  SPDX-License-Identifier: MIT
 
  @file ze.py
- @version v1.12-r1.12.14
+ @version v1.12-r1.12.15
 
  """
 import platform

diff --git a/include/ze_api.h b/include/ze_api.h
@@ -5,7 +5,7 @@
  * SPDX-License-Identifier: MIT
  *
  * @file ze_api.h
- * @version v1.12-r1.12.14
+ * @version v1.12-r1.12.15
  *
  */
 #ifndef _ZE_API_H

diff --git a/include/ze_ddi.h b/include/ze_ddi.h
@@ -5,7 +5,7 @@
  * SPDX-License-Identifier: MIT
  *
  * @file ze_ddi.h
- * @version v1.12-r1.12.14
+ * @version v1.12-r1.12.15
  *
  */
 #ifndef _ZE_DDI_H

diff --git a/include/zes.py b/include/zes.py
@@ -4,7 +4,7 @@
  SPDX-License-Identifier: MIT
 
  @file zes.py
- @version v1.12-r1.12.14
+ @version v1.12-r1.12.15
 
  """
 import platform

diff --git a/include/zes_api.h b/include/zes_api.h
@@ -5,7 +5,7 @@
  * SPDX-License-Identifier: MIT
  *
  * @file zes_api.h
- * @version v1.12-r1.12.14
+ * @version v1.12-r1.12.15
  *
  */
 #ifndef _ZES_API_H

diff --git a/include/zes_ddi.h b/include/zes_ddi.h
@@ -5,7 +5,7 @@
  * SPDX-License-Identifier: MIT
  *
  * @file zes_ddi.h
- * @version v1.12-r1.12.14
+ * @version v1.12-r1.12.15
  *
  */
 #ifndef _ZES_DDI_H

diff --git a/include/zet.py b/include/zet.py
@@ -4,7 +4,7 @@
  SPDX-License-Identifier: MIT
 
  @file zet.py
- @version v1.12-r1.12.14
+ @version v1.12-r1.12.15
 
  """
 import platform

diff --git a/include/zet_api.h b/include/zet_api.h
@@ -5,7 +5,7 @@
  * SPDX-License-Identifier: MIT
  *
  * @file zet_api.h
- * @version v1.12-r1.12.14
+ * @version v1.12-r1.12.15
  *
  */
 #ifndef _ZET_API_H

diff --git a/include/zet_ddi.h b/include/zet_ddi.h
@@ -5,7 +5,7 @@
  * SPDX-License-Identifier: MIT
  *
  * @file zet_ddi.h
- * @version v1.12-r1.12.14
+ * @version v1.12-r1.12.15
  *
  */
 #ifndef _ZET_DDI_H

diff --git a/source/layers/validation/README.md b/source/layers/validation/README.md
@@ -2,7 +2,7 @@
 
 ## Introduction
 
-The Level Zero driver implementations  [by design](https://spec.oneapi.io/level-zero/latest/core/INTRO.html#error-handling) do minimal error checking and do not guard against invalid API programming. 
+The Level Zero driver implementations  [by design](https://oneapi-src.github.io/level-zero-spec/level-zero/latest/core/INTRO.html#error-handling) do minimal error checking and do not guard against invalid API programming.
 
 The Level Zero Validation layer is intended to be the primary Level Zero API error handling mechanism. The validation layer can be enabled at runtime with environment settings. When validation layer is enabled, L0 loader will inject calls to validation layer into L0 API DDI tables. When validation layer is not enabled, it is completely removed from the call path and has no performance cost.  
 
@@ -19,9 +19,7 @@ By default, no validation modes will be enabled. The individual validation modes
 - `ZE_ENABLE_PARAMETER_VALIDATION`
 - `ZE_ENABLE_HANDLE_LIFETIME`
 - `ZEL_ENABLE_EVENTS_CHECKER`
-- `ZE_ENABLE_MEMORY_TRACKER` (Not yet Implemeneted)
-- `ZE_ENABLE_THREADING_VALIDATION` (Not yet Implemeneted)
-
+- `ZE_ENABLE_THREADING_VALIDATION` (Not yet Implemented)
 
 ## Validation Modes