Lines Matching refs:jump

54 probes work and how jump optimization works.  They explain certain
176 sysctl(8)), Kprobes tries to reduce probe-hit overhead by using a jump
192 - Kprobes verifies that the region that will be replaced by the jump
194   (A jump instruction is multiple bytes, and so may overlay multiple
198   jump into the optimized region.  Specifically:
200   - the function contains no indirect jump;
202     the fixup code triggered by the exception could jump back into the
204   - there is no near jump to the optimized region (other than to the first
220 - a jump back to the original execution path.
246 The Kprobe-optimizer doesn't insert the jump instruction immediately;
255 the optimized region with a jump instruction to the detour buffer,
264 optimized list.  If the optimization has been done, the jump is
269    the optimizer replaces the 2nd instruction with the jump *address*
279 The jump optimization changes the kprobe's pre_handler behavior.
316 - i386 (Supports jump optimization)
317 - x86_64 (AMD-64, EM64T) (Supports jump optimization)
644 a 5-byte jump instruction. So there are several limitations.
648 c) JTPR must not be targeted by any jump or call instruction.
786 a knob to globally and forcibly turn jump optimization (see section
787 :ref:`kprobes_jump_optimization`) ON or OFF. By default, jump optimization