Here is a list of constraints and limitations:
- Multiple instances of AMDuProfPcm can be launched in MSR mode (option
--msr) with the force reset option (-r), doing so might cause undefined behavior. - Sampling interval lower than 1 s (1000 ms) is not supported.
- MSR mode has significant overhead due to which the number of collected samples may not be equal to Profile duration/Sampling interval.
- In MSR mode, we can observe L3 Miss % to be > 100% when the number of L3 Accesses/Misses is low due to noise/inaccuracies.
- Undefined behavior if cores are turned off during a profile run.
- Heterogenous system configurations might cause undefined behavior.
- Hypervisors (from Cloud vendors) might restrict the guest from collecting some events due to security purposes, which leads to count values of these events being reported as 0.
- Limited support for Zen1 and Zen2 AMD processors.