Interpreting annotated disassembly code is not a simple task. The metrics that appear on a line with an instruction cannot usually be interpreted as metrics resulting from the execution of that instruction, for the following reasons.
For timing data, this means that the metric is "time spent waiting for this instruction to be issued", not "time spent executing this instruction".
Instructions that generate TLB misses are an exception. Because the load or store that triggered the TLB miss is retried after the miss is satisfied, metrics assigned to the load or store instruction can be interpreted as resulting from that instruction.
For hardware counters that count events relating to memory operations, the Collector performs a search for the instruction that triggered the event if the hardware counter name was prefixed with "+". If the search was successful, metrics are assigned to the PC that triggered the event.
See also | |
---|---|
The Disassembly Tab |