Skip to content

Commit dd15096

Browse files
committed
docs: Add missing snitch_occupancy metric
1 parent 4cd40eb commit dd15096

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

docs/ug/trace_analysis.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -128,6 +128,7 @@ In the following table you can find a complete list of all the performance metri
128128
|`snitch_issues` |Total number of instructions issued by Snitch, excluding those offloaded to the FPSS (see `snitch_fseq_offloads`). |
129129
|`snitch_fseq_offloads` |Total number of instructions offloaded by Snitch to the FPSS. |
130130
|`snitch_fseq_rel_offloads`|The ratio between `snitch_fseq_offloads` and the total number of instructions issued by Snitch core proper, i.e. `snitch_issues + snitch_fseq_offloads`. |
131+
|`snitch_occupancy` |IPC of the Snitch core, calculated as `snitch_issues / cycles`. |
131132
|`fpss_issues` |Total number of instructions issued by the FPSS. It counts repeated issues from the FREP sequencer. |
132133
|`fpss_fpu_issues` |Similar to `fpss_issues`, but counts only instructions destined to the FPU proper. It does not for instance include instructions issued to the FPSS's LSU. |
133134
|`fseq_yield` |The ratio between `fpss_issues` and `snitch_fseq_offloads`. The difference lies in the FREP sequencer possibly replicating instructions. If the sequencer is not used this ratio should amount to 1.|

0 commit comments

Comments
 (0)