Compare Arm and x86 top-down performance with PMU counters
Introduction
Analyze Intel x86 and Arm Neoverse top-down performance methodologies
Understand Intel x86 multilevel hierarchical top-down analysis
Understand Arm Neoverse top-down analysis
Evaluate cross-platform PMU counter differences
Measure performance with topdown-tool and Perf PMU counters
Next Steps
Compare Arm and x86 top-down performance with PMU counters
Introduction
Analyze Intel x86 and Arm Neoverse top-down performance methodologies
Understand Intel x86 multilevel hierarchical top-down analysis
Understand Arm Neoverse top-down analysis
Evaluate cross-platform PMU counter differences
Measure performance with topdown-tool and Perf PMU counters
Next Steps
Review frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Use Linux Perf on Intel x86 systems and
topdown-tool on Arm systems. Both systems need Perf. Arm systems also need topdown-tool.Save the code as
core-bound-div-chain.c, compile it with GCC or Clang, and run it as ./core-bound-div-chain <iterations>.The tools report Retiring, Bad Speculation, Frontend Bound, and Backend Bound. The FP64 divide-chain example is designed to show a prominent Backend Bound category.
Compare the top-level category percentages instead of raw event counts. Intel uses four issue slots per cycle, while Neoverse V2 uses eight rename slots. The accounting changes, but the category meanings remain comparable.
Verify that you ran the same benchmark with the same iteration count, using Perf on x86 and
topdown-tool on Arm. Microarchitecture and event-formula differences are expected, so focus on the relative distribution across the four categories.