-
Notifications
You must be signed in to change notification settings - Fork 4
Description
TLDR;
Is it possible to change kernel.perf_event_paranoid to be <= 1 so that --config threading will work with the latest AMDuProf version?
I tried using the preinstalled AMDuProf in /opt/AMDuProf_4.2-850 and mounted it into apptainer like so:
--bind /opt/AMDuProf_4.2-850:/opt/AMDuProf/
Some AMDuProf configs work such as this one:
/opt/AMDuProf/bin/AMDuProfCLI
profile
--config assess_ext
--detail
But for --config threading I get a segmentation fault:
Fatal Python error: Segmentation fault
Current thread 0x00007f69e375d880 (most recent call first):
File "/opt/conda/envs/py_3.10/lib/python3.10/subprocess.py", line 1796 in _execute_child
File "/opt/conda/envs/py_3.10/lib/python3.10/subprocess.py", line 971 in __init__
and for --config overview I see:
ERROR: Failed to read profile config file (/opt/AMDuProf/bin/Data/Profiles/0x19_0x1/overview.xml).
Next, I tried the latest version: 5.1.701 which works for --config assess_ext.
However for --config threading I see:
WARNING: For kernel.perf_event_paranoid >= 2, OS samples will not be collected for Core PMC based events.
ERROR: For non-root users, following perf_event_paranoid values are valid for Count mode Profiling:
<= 1 : for profiling launched application or already running processes
Please configure /proc/sys/kernel/perf_event_paranoid with appropriate value.
and for --config overview:
WARNING: For kernel.perf_event_paranoid >= 2, OS samples will not be collected for Core PMC based events.
ERROR: Run the script from uProf installed directory with root access : ./AMDuProfSetup.sh
else launch uProf with root access while collecting the profile data.
Would it be possible for at least the kernel.perf_event_paranoid value to be changed to be <= 1 so that --config threading will work with the latest AMDuProf version, and possibly even updating the cluster's installed version of the tool so that ./AMDuProfSetup.sh can be ran as root by an administrator?
Thanks!