Skip to content

Commit 3969f34

Browse files
authored
Update to spec v1.12.15 (#258)
* Fix Changelog and docs and update to v1.20.1 * Add v1.12.15 headers Signed-off-by: Neil R. Spruit <[email protected]>
1 parent 0d1f19d commit 3969f34

13 files changed

+29
-21
lines changed

CHANGELOG.md

+8
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,15 @@
11
# Level zero loader changelog
22

3+
## v1.20.1
4+
* Update to spec 1.12.15
5+
* Update Docs for spec links and corrections
36
## v1.20.0
47
* Update to spec 1.12
8+
* Allow pkg-config files on Windows as well
9+
* Fix GET_FUNCTION_PTR warnings on windows
10+
* Fix libddi table query code generation
11+
* Fixed pkg-config files generation
12+
* fixed potential memory leaks in events checker
513
## v1.19.2
614
* Remove static result in InitDrivers given first init fails
715
## v1.19.1

CMakeLists.txt

+1-1
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ if(MSVC AND (MSVC_VERSION LESS 1900))
1313
endif()
1414

1515
# This project follows semantic versioning (https://semver.org/)
16-
project(level-zero VERSION 1.20.0)
16+
project(level-zero VERSION 1.20.1)
1717

1818
include(GNUInstallDirs)
1919

CONTRIBUTING.md

+9-7
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ review these for proper alignment with the
2020

2121
* The functionality in the Level Zero Loader and layers which follow the Level Zero spec must follow these naming conventions:
2222

23-
* https://spec.oneapi.io/level-zero/latest/core/INTRO.html#naming-convention
23+
* https://oneapi-src.github.io/level-zero-spec/level-zero/latest/core/INTRO.html#naming-convention
2424

2525
* If the contributions are adding new functionality unique to the Level Zero Loader (ie not Level Zero Spec related):
2626
* 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:
3636
* Clone the specification repo: `git clone https://github.com/oneapi-src/level-zero-spec.git level-zero-spec`
3737
* Checkout the specification version in the specification repo, for example:
3838
* `cd level-zero-spec`
39-
* `git checkout v1.5`
40-
* Generate the specification JSON file:
41-
* `cd ./scripts`
42-
* `python3 ./run.py --debug '--!html' '--!rst' '--!build' --ver 1.5`
39+
* `git checkout v1.12.15`
40+
* Generate the specification JSON file and Headers:
41+
* `cd level-zero-spec/scripts`
42+
* `python3 ./run.py --debug '--!html' '--!rst' '--!build' --ver 1.12`
43+
* Copy the Headers From Spec to Loader repo
44+
* `cp level-zero-spec/include/* level-zero/include/`
4345
* Execute the json2src script in the level-zero repo with the input.json in the specification repo with the corresponding spec version, for example:
44-
* `./scripts/json2src.py --ver 1.5 --api-json <path to level-zero-spec checkout>/scripts/input.json .`
46+
* `./level-zero/scripts/json2src.py --ver 1.12 --api-json level-zero-spec/scripts/input.json .`
4547

4648
These scripts update the code with what would be generated in the next specification update.
4749

@@ -56,7 +58,7 @@ When performing a code review please refer to this checklist to guide your comme
5658

5759
* Does the code follow C++ Coding Standards? [C++ Coding Standards](#c-coding-standards).
5860
* Does the code follow the Level Zero naming conventions? [Naming Conventions](#naming-conventions).
59-
* Does the code follow the Level Zero specification? See here for the latest spec: https://spec.oneapi.io/level-zero/latest/index.html.
61+
* 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.
6062
* Is the code for the Validation Layer? Please review the following: [Validation Layer README](source/layers/validation/README.md).
6163
* Is the code for the Tracing Layer? Please review the following: [Tracing Layer README](source/layers/tracing/README.md).
6264
* 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?

include/ze.py

+1-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
SPDX-License-Identifier: MIT
55
66
@file ze.py
7-
@version v1.12-r1.12.14
7+
@version v1.12-r1.12.15
88
99
"""
1010
import platform

include/ze_api.h

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
* SPDX-License-Identifier: MIT
66
*
77
* @file ze_api.h
8-
* @version v1.12-r1.12.14
8+
* @version v1.12-r1.12.15
99
*
1010
*/
1111
#ifndef _ZE_API_H

include/ze_ddi.h

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
* SPDX-License-Identifier: MIT
66
*
77
* @file ze_ddi.h
8-
* @version v1.12-r1.12.14
8+
* @version v1.12-r1.12.15
99
*
1010
*/
1111
#ifndef _ZE_DDI_H

include/zes.py

+1-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
SPDX-License-Identifier: MIT
55
66
@file zes.py
7-
@version v1.12-r1.12.14
7+
@version v1.12-r1.12.15
88
99
"""
1010
import platform

include/zes_api.h

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
* SPDX-License-Identifier: MIT
66
*
77
* @file zes_api.h
8-
* @version v1.12-r1.12.14
8+
* @version v1.12-r1.12.15
99
*
1010
*/
1111
#ifndef _ZES_API_H

include/zes_ddi.h

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
* SPDX-License-Identifier: MIT
66
*
77
* @file zes_ddi.h
8-
* @version v1.12-r1.12.14
8+
* @version v1.12-r1.12.15
99
*
1010
*/
1111
#ifndef _ZES_DDI_H

include/zet.py

+1-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
SPDX-License-Identifier: MIT
55
66
@file zet.py
7-
@version v1.12-r1.12.14
7+
@version v1.12-r1.12.15
88
99
"""
1010
import platform

include/zet_api.h

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
* SPDX-License-Identifier: MIT
66
*
77
* @file zet_api.h
8-
* @version v1.12-r1.12.14
8+
* @version v1.12-r1.12.15
99
*
1010
*/
1111
#ifndef _ZET_API_H

include/zet_ddi.h

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
* SPDX-License-Identifier: MIT
66
*
77
* @file zet_ddi.h
8-
* @version v1.12-r1.12.14
8+
* @version v1.12-r1.12.15
99
*
1010
*/
1111
#ifndef _ZET_DDI_H

source/layers/validation/README.md

+2-4
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
## Introduction
44

5-
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.
5+
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.
66

77
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.
88

@@ -19,9 +19,7 @@ By default, no validation modes will be enabled. The individual validation modes
1919
- `ZE_ENABLE_PARAMETER_VALIDATION`
2020
- `ZE_ENABLE_HANDLE_LIFETIME`
2121
- `ZEL_ENABLE_EVENTS_CHECKER`
22-
- `ZE_ENABLE_MEMORY_TRACKER` (Not yet Implemeneted)
23-
- `ZE_ENABLE_THREADING_VALIDATION` (Not yet Implemeneted)
24-
22+
- `ZE_ENABLE_THREADING_VALIDATION` (Not yet Implemented)
2523

2624
## Validation Modes
2725

0 commit comments

Comments
 (0)