You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow the user to configure contentious component pairs (e.g., rocm &
rocp_sdk, rocm_smi & amd_smi), but only allow one from each pair to be
active at runtime. The ROCm version determines which components are
active by default. This can be overridden by the PAPI_DISABLE_COMPONENTS
environment variable.
These changes have been tested using ROCm 7.0.2 on the Frontier
supercomputer, which contains the AMD MI250X architecture.
Copy file name to clipboardExpand all lines: src/components/amd_smi/README.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,3 +107,10 @@ After changing `PAPI_AMDSMI_ROOT` or related library paths, rerun make clobber &
107
107
108
108
## Hardware and Software Support
109
109
To see the `amd_smi` component's current supported hardware and software please visit the GitHub wiki page [Hardware and Software Support - AMD\_SMI Component](https://github.com/icl-utk-edu/papi/wiki/Hardware-and-Software-Support-%E2%80%90-AMD_SMI-Component).
110
+
111
+
## Known Limitations
112
+
113
+
* For AMD devices older than the AMD Instinct MI300A, PAPI should not be configured with both `rocm_smi` and `amd_smi`.
114
+
If both components are configured, then `rocm_smi` will be active by default for ROCm < 6.4.0; `amd_smi` will be active by default for ROCm >= 6.4.0.
115
+
Users can override this when running an application by setting `export PAPI_DISABLE_COMPONENTS=rocm_smi` when `rocm_smi` is active by default, or
116
+
`export PAPI_DISABLE_COMPONENTS=amd_smi` when `amd_smi` is active by default.
Copy file name to clipboardExpand all lines: src/components/rocp_sdk/README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,5 +65,9 @@ To see the ROCP\_SDK component's current supported hardware and software please
65
65
66
66
## Known Limitations
67
67
68
+
* For AMD devices older than the AMD Instinct MI300A, PAPI should not be configured with both `rocm` and `rocp_sdk`.
69
+
If both components are configured, then `rocm` will be active by default for ROCm < 6.3.2; `rocp_sdk` will be active by default for ROCm >= 6.3.2.
70
+
Users can override this when running an application by setting `export PAPI_DISABLE_COMPONENTS=rocm` when `rocm` is active by default, or
71
+
`export PAPI_DISABLE_COMPONENTS=rocp_sdk` when `rocp_sdk` is active by default.
68
72
* In dispatch mode, PAPI may read zeros if reading takes place immediately after the return of a GPU kernel. This is not a PAPI bug. It may occur because calls such as hipDeviceSynchronize() do not guarantee that ROCprofiler has been called and all counter buffers have been flushed. Therefore, it is recommended that the user code adds a delay between the return of a kernel and calls to PAPI_read(), PAPI_stop(), etc.
69
73
* If an application is linked against the static PAPI library libpapi.a, then the application must call PAPI_library_init() before calling any hip routines (e.g. hipInit(), hipGetDeviceCount(), hipLaunchKernelGGL(), etc). If the application is linked against the dynamic library libpapi.so, then the order of operations does not matter.
0 commit comments