oneapi-src / oneapi-src/level-zero
zesDeviceProcessesGetState API cannot get the process state of a specific device.
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 335
- Forks
- 140
- Avg merge
- 12h 32m
- Merged PRs (30d)
- 5
Description
- two Arc GPUs on ubuntu OS
- write a sycl vector-add code and bind queue to the device GPU:0
- run the program and monitor by
zesDeviceProcessesGetState zesDeviceProcessesGetStateshows
- ./test-add should be under device gpu0. And it cannot be get process info from device gpu1.
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.
Research direction
Start by reproducing the two-Arc-GPU scenario on Ubuntu with the SYCL vector-add program bound to GPU:0, then monitor it with zesDeviceProcessesGetState. The issue is done when ./test-add is reported under GPU0 and no process information is reported for GPU1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux, ubuntu
- Domain
- api, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100