System information

108 System Analysis and Tuning Guide
opreport
Overflow stats not available
CPU: CPU with timer interrupt, speed 0 MHz (estimated)
Profiling through timer interrupt
TIMER:0|
samples| %|
------------------
84877 98.3226 no-vmlinux
...
8 Shutdown the OProfile daemon:
opcontrol --shutdown
8.4.2 Getting Event Configurations
The general procedure for event configuration is as follows:
1 Use first the events CPU-CLK_UNHALTED and INST_RETIRED to find opti-
mization opportunities.
2 Use specific events to find bottlenecks. To list them, use the command opcon-
trol --list-events.
If you need to profile certain events, first check the available events supported by
your processor with the ophelp command (example output generated from Intel
Core i5 CPU):
ophelp
oprofile: available events for CPU type "Intel Architectural Perfmon"
See Intel 64 and IA-32 Architectures Software Developer's Manual
Volume 3B (Document 253669) Chapter 18 for architectural perfmon events
This is a limited set of fallback events because oprofile doesn't know your
CPU
CPU_CLK_UNHALTED: (counter: all))
Clock cycles when not halted (min count: 6000)
INST_RETIRED: (counter: all))
number of instructions retired (min count: 6000)
LLC_MISSES: (counter: all))
Last level cache demand requests from this core that missed the LLC
(min count: 6000)
Unit masks (default 0x41)
----------
0x41: No unit mask
LLC_REFS: (counter: all))
Last level cache demand requests from this core (min count: 6000)
Unit masks (default 0x4f)