Parameter validation layer erroneously checks pCommandQueueGroupProperties
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- api, testing-qa
Research direction
Start at source/layers/validation/parameter_validation/ze_parameter_validation.cpp around line 292 and trace validation for zeDeviceGetCommandQueueGroupProperties(). Reproduce the call with the validation layer enabled, then verify that an application need not preinitialize ze_command_queue_group_properties_t::stype and that the function populates pCommandQueueGroupProperties without returning ZE_RESULT_ERROR_INVALID_ARGUMENT.
Written by the indexing model from the issue text.
Description
I'm seeing some unexpected behavior with the parameter validation layer enabled.
Expected behavior:
Calling zeDeviceGetCommandQueueGroupProperties() populates the memory pointed to by the pCommandQueueGroupProperties parameter.
Actual behavior:
Calling zeDeviceGetCommandQueueGroupProperties() returns ZE_RESULT_ERROR_INVALID_ARGUMENT.
Comments
The issue is that the validation layer expects the ze_command_queue_group_properties_t::stype field to be set by the application. However, it is the responsibility of the zeDeviceGetCommandQueueGroupProperties() function to initialize the data. The work-around is for the application to partially initialize the data by setting all ze_command_queue_group_properties_t::stype fields before calling zeDeviceGetCommandQueueGroupProperties().
I think this is the offending line, and I suspect the solution is just to remove it.
- Dominant language
- C++
- Stars
- 335
- Forks
- 140
- Avg merge
- 12h 32m
- Merged PRs (30d)
- 5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from oneapi-src/level-zero
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
oneapi-src/level-zero#495 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oneapi-src/level-zero#485 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
oneapi-src/level-zero#447 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
oneapi-src/level-zero#482 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
oneapi-src/level-zero#419 ·
All issues in oneapi-src/level-zero
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100