level-zero icon indicating copy to clipboard operation
level-zero copied to clipboard

oneAPI Level Zero Specification Headers and Loader

Results 104 level-zero issues
Sort by recently updated
recently updated
newest added

This is a question about the Level Zero API. I have the following sequence of instructions in which I accidentally forgot to `reset`. Once the command list is closed, I...

https://github.com/oneapi-src/level-zero/blob/0d30b1fa712253c68bfdfa3863d380df4301b8a4/CMakeLists.txt#L111

The current implementation of zesDeviceGetProperties() return "Unknown" instead of "unkown" as stated in the documentation. I assume the documentation is wrong. I updated the documentation of zes_fabric_port_properties_t as well even...

Build makes invalid assumptions about Git repository tags / content: ``` $ git clone --branch v0.91.21 --depth 1 https://github.com/oneapi-src/level-zero.git && cd level-zero && cmake -Wno-dev -G Ninja -DCMAKE_BUILD_TYPE=Release . Cloning...

The API for zeCommandListAppendWaitOnEvents is analogous to clEnqueuMarkerWithWaitList in OpenCL There are a couple of issues 1) There is no information on how the Level Zero API behaves when the...

While level 0 has fences and events it doesn't appear to have any semaphore support. Events can be a messy solution from a scheduler point of view, as they pretty...

This isn't really an issue, it's more of an FYI to level0 developers. In the piglit open source testing project we have a bunch of CL program tests. These tests...

(https://github.com/oneapi-src/level-zero/releases) shows that only 20.12.16259 is supported. Can level-zero loader support more up-to-date version such as 20.21.16886? Thanks

The spec doesn't seem to explicitly say this but kernel objects are currently defined should be generated from modules per command recording thread. I wonder if it would be better...

From https://spec.oneapi.com/versions/0.7/oneL0/core/PROG.html#images: > This methodology allows for device-specific encoding of image contents (e.g., tile swizzle patterns, lossless compression, etc.) and avoids exposing these details in the API in a backwards...