Lines Matching refs:instructions
25 samples output by perf hardware events, for example as though the "instructions"
111 There are two ways that instructions-per-cycle (IPC) can be calculated depending
121 of instructions and number of cycles since the last update, and thus represent
123 events is calculated separately from IPC for "instructions" events.
134 value, "instructions" events can be used e.g. --itrace=i0ns
750 i synthesize "instructions" events
764 instructions".
773 Note that "instructions", "branches" and "transactions" events depend on code
811 decoded packets and instructions. Note that this option slows down the decoder
814 In addition, the period of the "instructions" event can be specified. e.g.
820 "ns" (nanoseconds), "t" (TSC ticks) or "i" (instructions).
834 'instructions' (i.e. --itrace=i1i).
836 Also the call chain size (default 16, max. 1024) for instructions or
842 Also the number of last branch entries (default 64, max. 1024) for instructions or
853 It is also possible to skip events generated (instructions, branches, transactions)
858 skips the first million instructions.