pcm.x error with Xeon Gold 6154

pcm.x error with Xeon Gold 6154


I had been using pcm.x from PCM2.11 package. Recently, I tried it on Xeon Gold 6154 (Skylake) and got following errors. I ran the command on Ubuntu 16.4 with kernel 4.9.16. Since Skylake is supported by PCM2.11, is there any special configuration I need done for Gold 6154?




root@msl-dpe-perf65:/home/harry.li/tools/IntelPerformanceCounterMonitor-V2.11# ./pcm.x

 Intel(r) Performance Counter Monitor V2.11 (2016-04-20 12:01:09 +0200 ID=56de28a)

 Copyright (c) 2009-2016 Intel Corporation

Error: unsupported processor. Only Intel(R) processors are supported (Atom(R) and microarchitecture codename Nehalem/Nehalem-EP, Atom(tm), Westmere/Clarkdale, Sandy Bridge, Westmere-EP, Sandy Bridge-EP/Jaketown, Nehalem-EX, Westmere-EX, Ivy Bridge, Haswell, Broadwell, Ivy Bridge-EP/EN/EX/Ivytown, Haswell-EP/EN/EX, Broadwell-EP, Broadwell-DE, Skylake). CPU model number: 85 Brand: "Intel(R) Xeon(R) Gold 6154 CPU @ 3.00GHz"
Access to Intel(r) Performance Counter Monitor has denied (no MSR or PCI CFG space access).
root@msl-dpe-perf65:/home/harry.li/tools/IntelPerformanceCounterMonitor-V2.11# lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                72
On-line CPU(s) list:   0-71
Thread(s) per core:    2
Core(s) per socket:    18
Socket(s):             2
NUMA node(s):          2
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 85
Model name:            Intel(R) Xeon(R) Gold 6154 CPU @ 3.00GHz
Stepping:              4
CPU MHz:               1200.000
CPU max MHz:           3001.0000
CPU min MHz:           1200.0000
BogoMIPS:              6002.28
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              1024K
L3 cache:              25344K
NUMA node0 CPU(s):     0-17,36-53
NUMA node1 CPU(s):     18-35,54-71
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts pku ospke

3 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Intel's inconsistency in nomenclature strikes again....

According to https://software.intel.com/en-us/articles/intel-performance-counter-monitor, PCM 2.9 and later support the Skylake "Core" processors, with PCM 2.10 adding support for the Skylake U and Y models.  PCM 2.11 adds support for Xeon E5 v4 (Broadwell EP -- not Skylake EP).   See https://en.wikipedia.org/wiki/Skylake_(microarchitecture) for a few more details.

When reading older reviews, note that Intel does not use the "Skylake EP" and "Skylake EX" nomenclature -- these are both now called "Xeon Scalable Processors".  My unofficial interpretation: Models that would have been called "Skylake EP" under the old naming scheme are now called "Xeon Scalable Bronze" and "Xeon Scalable Gold 5xxx", while models that would have been called "Skylake EX" are now called "Xeon Scalable Gold 6xxx" and "Xeon Scalable Platinum".

"Dr. Bandwidth"

"intel Performance Counter Monitor" has been discontinued. Instead, we are now contributing to the fork "Processor Counter Monitor" on github.

In patricular, we have recently pushed the necessary changes for the Intel Xeon processors based on Skylake architecture. Please pull the latest sources from there and it should work on your processor. In case you run into problems, please let us know.

Leave a Comment

Please sign in to add a comment. Not a member? Join today