Sample Instructions with WindowsPerf and Arm SPE
Introduction
Overview of Arm Statistical Profiling Extension
Setup
WindowsPerf Sample using SPE
WindowsPerf Record using SPE
Summary
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

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 WindowsPerf build should I use to profile with Arm SPE?
Use the SPE-enabled build included in WindowsPerf release 3.8.0. Download the release asset and select the WindowsPerf build in the SPE/ subdirectory.
Do I need a debug build of CPython for this path?
Yes. The examples use python_d.exe, which you build from CPython sources in debug mode for Windows on Arm (AArch64).
How do I pass Python arguments without wperf parsing them?
Use -- to separate wperf options from the arguments passed to python_d.exe. Everything after -- is forwarded to the Python process.
Why pin the CPython process to one CPU core, and which core is used?
Pinning keeps the workload on a known CPU so collected samples map to that core consistently. Pin the process to core 1.
What result should I expect after running wperf record with an SPE event?
WindowsPerf records SPE load events for the run. Use the --annotate and --disassemble options to review where sampled instructions map to source code and assembly.

Share

Tell others about this Learning Path.

Back