oneapi-src / oneapi-src/level-zero

ZE_RESULT_ERROR_UNSUPPORTED_FEATURE when running zeDeviceGetStatus

Open
#102 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
335
Forks
140
Avg merge
12h 32m
Merged PRs (30d)
5

Description

Running the function zeDeviceGetStatus produces the error code 78000003, which is ZE_RESULT_ERROR_UNSUPPORTED_FEATURE.

    result = zeDeviceGetStatus(device);
    if (result != ZE_RESULT_SUCCESS) {
        std::cout << "[JNI] Error in zeDeviceGetStatus with code: " << std::hex << result << std::dec << std::endl;
        if (result == ZE_RESULT_ERROR_UNSUPPORTED_FEATURE) {
            std::cout << "[JNI] Error ZE_RESULT_ERROR_UNSUPPORTED_FEATURE " << std::endl;
        }
    }

Output of this snippet:

[JNI] Error in zeDeviceGetStatus with code: 78000003
[JNI] Error ZE_RESULT_ERROR_UNSUPPORTED_FEATURE 

However, following the Level Zero SPEC, https://spec.oneapi.io/level-zero/latest/core/api.html?highlight=zedevicegetstatus#zedevicegetstatus, this function does not return such as error code.

Does this function need hardware support? Is this an error in the implementation?

Some context:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the zeDeviceGetStatus entry point and compare its returned codes with the linked Level Zero specification, using the stated Compute-Runtime and UHD Graphics 770 context. Determine whether ZE_RESULT_ERROR_UNSUPPORTED_FEATURE is expected hardware behavior or an implementation/specification discrepancy, then document the conclusion and any required correction.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.