[UR][L0v2] Bump Level Zero and use stable graph API#22489
Conversation
2ebbe2d to
b051432
Compare
b051432 to
442882e
Compare
d6b19c1 to
5ff5644
Compare
| @@ -8,17 +8,18 @@ | |||
| //===----------------------------------------------------------------------===// | |||
|
|
|||
| #include "graph.hpp" | |||
| #include "../external/driver_experimental/zex_graph.h" | |||
| // #include "../external/driver_experimental/zex_graph.h" | |||
| #include "../ur_interface_loader.hpp" | ||
| #include "common.hpp" | ||
| #include "context.hpp" | ||
| #include <level_zero/ze_api.h> |
There was a problem hiding this comment.
move this include to the top of the list
|
@mateuszpn, I guess that CI tests either only the experimental or stable path, could you check locally whether both paths are working. |
2a50a02 to
1b7eb49
Compare
1b7eb49 to
058180e
Compare
Both paths are working (checked on CI with NEO released driver — experimental path and locally with closed driver 39158 — stable path). The only problem is a bug in the driver (both NEO and closed, but surfaced only in the latter). The DDI table reports version 1_16, while functions like zeCommandListBeginGraphCaptureExt require 1_17. The loader rejects these calls with UNSUPPORTED_VERSION before they reach the driver, which is incorrect — the driver does support these functions. This prevents the functions from running, and there are e2e graph tests which fail for this reason. Old path omits the validation. |
|
@kswiecicki @KFilipek Both paths work locally. Quick patch from driver team + today's commit to the PR solved all issues. |
|
CI Windows failure is caused by #22293, the macOS failure is caused by an issue with the runner platform. |
This PR bumps the Level Zero to the 1.32.0 and use the stable Level Zero graph API.