Lines Matching refs:IPC
147 There are two ways that instructions-per-cycle (IPC) can be calculated depending
150 If the 'cyc' config term (see config terms section below) was used, then IPC is
158 the average IPC since the last IPC for that event type. Note IPC for "branches"
159 events is calculated separately from IPC for "instructions" events.
161 Even with the 'cyc' config term, it is possible to produce IPC information for
165 The number of instructions is known, but if IPC is reported, cycles can be too
166 low and so IPC is too high. Note that inaccuracy decreases as the period of
172 Also note that the IPC instruction count may or may not include the current
179 presently sampled, so IPC values for them do not appear e.g. a CYC packet with a
180 TNT packet that starts with a non-taken branch. To see every possible IPC
916 A approximate IPC
1277 However, IPC can still be determined, hence cyc=1 can be added.
1300 …ffffffff82133c42 vmx_vmenter+0x2 ([kernel.kallsyms]) vmresume IPC: 0.11 (50/445)
1302 …ffbb678b0b native_write_msr+0xb ([guest.kernel.kallsyms]) retq IPC: 0.04 (2/41)
1306 …ffbb66664b lapic_next_deadline+0x2b ([guest.kernel.kallsyms]) retq IPC: 0.16 (4/25)
1308 …rogram_event+0x91 ([guest.kernel.kallsyms]) jz 0xffffffffbb74603c IPC: 0.06 (2/30)
1340 IPC can be determined, hence cyc=1 can be added.
1401 …fffffff82133c42 vmx_vmenter+0x2 ([kernel.kallsyms]) vmresume IPC: 0.05 (40/769)