Give feedback

How would you rate this Learning Path?

Review frequently asked questions

AI-assisted

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.

Close
?
Which tool should I use to collect top-down metrics on each system?
Use Linux Perf on Intel x86 systems and topdown-tool on Arm systems. Both systems need Perf. Arm systems also need topdown-tool.
How do I build and run the example benchmark?
Save the code as core-bound-div-chain.c, compile it with GCC or Clang, and run it as ./core-bound-div-chain <iterations>.
What result should I expect when I profile the example workload?
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.
How do I compare results across Intel and Arm given different slot definitions?
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.
What should I check if my Intel and Arm breakdowns look very different?
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.

Share

Tell others about this Learning Path.

Back