Lines Matching full:optimized

193   instruction (the "optimized region") lies entirely within one function.
198   jump into the optimized region.  Specifically:
203     optimized region -- Kprobes checks the exception tables to verify this);
204   - there is no near jump to the optimized region (other than to the first
207 - For each instruction in the optimized region, Kprobes verifies that
219 - the instructions from the optimized region
229 - Other instructions in the optimized region are probed.
236 If the kprobe can be optimized, Kprobes enqueues the kprobe to an
238 it.  If the to-be-optimized probepoint is hit before being optimized,
249 optimized region [3]_.  As you know, synchronize_rcu() can ensure
255 the optimized region with a jump instruction to the detour buffer,
261 When an optimized kprobe is unregistered, disabled, or blocked by
264 optimized list.  If the optimization has been done, the jump is
282 is optimized, that modification is ignored.  Thus, if you want to
539 a probepoint for which there is a post_handler cannot be optimized.
540 So if you install a kprobe with a post_handler, at an optimized
579 kretprobe handlers and optimized kprobe handlers run without interrupt
665 Optimized Probe Overhead
668 Typically, an optimized kprobe hit takes 0.07 to 0.1 microseconds to
671   k = unoptimized kprobe, b = boosted (single-step skipped), o = optimized kprobe,
672   r = unoptimized kretprobe, rb = boosted kretprobe, ro = optimized kretprobe.
752 such probes are marked with [DISABLED]. If the probe is optimized, it is
753 marked with [OPTIMIZED]. If the probe is ftrace-based, it is marked with
775 "debug.kprobes_optimization" to 0 via sysctl, all optimized probes will be
776 unoptimized, and any new probes registered after that will not be optimized.
778 Note that this knob *changes* the optimized state. This means that optimized
779 probes (marked [OPTIMIZED]) will be unoptimized ([OPTIMIZED] tag will be
780 removed). If the knob is turned on, they will be optimized again.