rdementi
commented
6 days ago hi, is it also happening with the latest version from the master branch? Are you running it under root?
Open wynnfeng opened 1 week ago
rdementi
commented
6 days ago hi, is it also happening with the latest version from the master branch? Are you running it under root?
wynnfeng
commented
5 days ago hi, is it also happening with the latest version from the master branch? Are you running it under root?
I just test, the master branch doesn't have this problem, its output is here:
[2024-09-13 10:44:57]>/usr/sbin/pcm-latency --help
Intel(r) Performance Counter Monitor ($Format:%ci ID=%h$)
This utility measures Latency information
Usage:
-h | --help | /h => print this help and exit
--PMM | -pmm => to enable PMM (Default DDR uncore latency)
-i[=number] | /i[=number] => allow to determine number of iterations
-silent => silence information output and print only measurements
--version => print application version
-v | --verbose => verbose Outputwhich commit fix this problem?
wynnfeng
commented
5 days ago hi, is it also happening with the latest version from the master branch? Are you running it under root?
the promblem occur at version 202405:https://github.com/intel/pcm/archive/refs/tags/202405.tar.gz and when I run it under root, it won't core dumped, but other error is same
[2024-09-13 10:47:36]>sudo /usr/sbin/pcm-latency --help
Detected a hypervisor/virtualization technology. Some metrics might not be available due to configuration or availability of virtual hardware features.
===== Processor information =====
Linux arch_perfmon flag : yes
Hybrid processor : no
IBRS and IBPB supported : yes
STIBP supported : yes
Spec arch caps supported : yes
Max CPUID level : 22
CPU model number : 85
INFO: Reducing the number of programmable counters to 3 to workaround the fixed cycle counter virtualization issue on AWS.
You can disable the workaround by setting PCM_NO_AWS_WORKAROUND=1 environment variable
Number of physical cores: 4
Number of logical cores: 4
Number of online logical cores: 4
Threads (logical cores) per physical core: 1
Num sockets: 4
Physical cores per socket: 1
Last level cache slices per socket: 0
Core PMU (perfmon) version: 2
Number of core PMU generic (programmable) counters: 3
Width of generic (programmable) counters: 48 bits
Number of core PMU fixed counters: 3
Width of fixed counters: 48 bits
Nominal core frequency: 2500000000 Hz
IBRS enabled in the kernel : yes
STIBP enabled in the kernel : no
The processor is not susceptible to Rogue Data Cache Load: yes
The processor supports enhanced IBRS : yes
Package thermal spec power: 0 Watt; Package minimum power: 0 Watt; Package maximum power: 0 Watt;
Can't open MCFG table. Check permission of /sys/firmware/acpi/tables/MCFG
Can't open MCFG table. Check permission of /sys/firmware/acpi/tables/MCFG1
Can't open MCFG table. Check permission of /pcm/sys/firmware/acpi/tables/MCFG
Can't open MCFG table. Check permission of /pcm/sys/firmware/acpi/tables/MCFG1
WARNING: enumeration of devices in UncorePMUDiscovery failed
INFO: Linux perf interface to program uncore PMUs is NOT present
Can't open MCFG table. Check permission of /sys/firmware/acpi/tables/MCFG
Can't open MCFG table. Check permission of /sys/firmware/acpi/tables/MCFG1
Can't open MCFG table. Check permission of /pcm/sys/firmware/acpi/tables/MCFG
Can't open MCFG table. Check permission of /pcm/sys/firmware/acpi/tables/MCFG1
Can not access server uncore PCI configuration space. Access to uncore counters (memory and QPI bandwidth) is disabled.
You must be root to access server uncore counters in PCM.
Can't open MCFG table. Check permission of /sys/firmware/acpi/tables/MCFG
Can't open MCFG table. Check permission of /sys/firmware/acpi/tables/MCFG1
Can't open MCFG table. Check permission of /pcm/sys/firmware/acpi/tables/MCFG
Can't open MCFG table. Check permission of /pcm/sys/firmware/acpi/tables/MCFG1
terminate called after throwing an instance of 'std::exception'
what(): std::exception
Abortedhi, is it also happening with the latest version from the master branch? Are you running it under root?
I just test, the master branch doesn't have this problem, its output is here:
[2024-09-13 10:44:57]>/usr/sbin/pcm-latency --help Intel(r) Performance Counter Monitor ($Format:%ci ID=%h$) This utility measures Latency information Usage: -h | --help | /h => print this help and exit --PMM | -pmm => to enable PMM (Default DDR uncore latency) -i[=number] | /i[=number] => allow to determine number of iterations -silent => silence information output and print only measurements --version => print application version -v | --verbose => verbose Outputwhich commit fix this problem?
I think this commit is relevant here: https://github.com/intel/pcm/commit/f92b55caa070ec9145219a383a0d3d8e2a5e8563
wynnfeng
commented
4 days ago hi, is it also happening with the latest version from the master branch? Are you running it under root?
I just test, the master branch doesn't have this problem, its output is here:
[2024-09-13 10:44:57]>/usr/sbin/pcm-latency --help Intel(r) Performance Counter Monitor ($Format:%ci ID=%h$) This utility measures Latency information Usage: -h | --help | /h => print this help and exit --PMM | -pmm => to enable PMM (Default DDR uncore latency) -i[=number] | /i[=number] => allow to determine number of iterations -silent => silence information output and print only measurements --version => print application version -v | --verbose => verbose Outputwhich commit fix this problem?
I think this commit is relevant here: f92b55c
It fixes, thanks!
when I excute
/usr/sbin/pcm-latency --help, it aborted with core dumped, Is this exit considered normal? the version of pcm is 202405