zesDeviceProcessesGetState API cannot get the process state of a specific device.

Open
#283 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

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.

Description

  1. two Arc GPUs on ubuntu OS
  2. write a sycl vector-add code and bind queue to the device GPU:0
  3. run the program and monitor by zesDeviceProcessesGetState
  4. zesDeviceProcessesGetState shows

Image

  1. ./test-add should be under device gpu0. And it cannot be get process info from device gpu1.
Dominant language
C++
Stars
335
Forks
140
Avg merge
12h 32m
Merged PRs (30d)
5

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.

More from oneapi-src/level-zero

All issues in oneapi-src/level-zero

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.