You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ug/trace_analysis.md
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -128,6 +128,7 @@ In the following table you can find a complete list of all the performance metri
128
128
|`snitch_issues`|Total number of instructions issued by Snitch, excluding those offloaded to the FPSS (see `snitch_fseq_offloads`). |
129
129
|`snitch_fseq_offloads`|Total number of instructions offloaded by Snitch to the FPSS. |
130
130
|`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`. |
131
132
|`fpss_issues`|Total number of instructions issued by the FPSS. It counts repeated issues from the FREP sequencer. |
132
133
|`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. |
133
134
|`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