9a82118c85a69c25f5202dee84d59e5f306c1681
The ROCclr assigns zero-based IDs to GPUs in the order they are discovered. That zero-based ID is what is used to identify the GPU on which the HIP_OPS activity took place. When multiple ranks are used, each rank's first logical device always has GPU ID 0, regardless of which physical device is selected with CUDA_VISIBLE_DEVICES. Because of this, when merging trace files from multiple ranks, GPU IDs from different processes may overlap. The long term solution is to use the KFD's gpu_id which is stable across APIs and processes. Unfortunately the gpu_id is not yet exposed by the ROCr, so for now use the driver's node id. Change-Id: Ib78854527d600d175bb76e2df0747c33f898c615
SWDEV-362046 - Report HIP_OPS activities using the ROCr driver_node_id instead of the device's index
Descrizione
No description provided
Languages
C++
67.5%
C
20.6%
Python
6.6%
CMake
3.4%
Shell
0.6%
Altro
1.1%