Building ROCmInfo

Building ROCmInfo#

Use the standard cmake build procedure to build ROCmInfo. The location of ROCm root (parent directory containing ROCM headers and libraries) must be provided as a CMake argument using the standard CMAKE_PREFIX_PATH CMake variable.

After cloning the ROCmInfo git repo, you must perform a git-fetch –tags to get the tags residing on the repo. These tags are used for versioning.

For example,

$ git fetch --tags origin

Building from the CMakeLists.txt directory might look like this:

mkdir -p build

cd build

cmake -DCMAKE_PREFIX_PATH=/opt/rocm ..

make

cd ..

Upon a successful build, the binary, ROCmInfo, and the Python script, rocm_agent_enumerator, will be in the build folder.

ROCmInfo execution#

“rocminfo” gives information about the HSA system attributes and agents.

“rocm_agent_enumerator” prints the list of available AMD GCN ISA or architecture names. With the option ‘-name’, it prints out available architectures names obtained from ROCmInfo. Otherwise, it generates ISA in one of five different ways:

  1. ROCM_TARGET_LST : a user defined environment variable, set to the path and filename where to find the “target.lst” file. This can be used in an install environment with sandbox, where execution of “rocminfo” is not possible.

  2. target.lst : user-supplied text file, in the same folder as “rocm_agent_enumerator”. This is used in a container setting where ROCm stack may usually not available.

  3. HSA topology : gathers the information from the HSA node topology in /sys/class/kfd/kfd/topology/nodes/

  4. lspci : enumerate PCI bus and locate supported devices from a hard-coded lookup table.

  5. ROCmInfo : a tool shipped with this script to enumerate GPU agents available on a working ROCm stack.