Lines Matching +full:self +full:- +full:describing

30   - The kernel probes are the most generic. The code can be redirected by
33   - The function tracer calls the code from a predefined location that is
35     compiler using the '-pg' gcc option.
37   - Livepatching typically needs to redirect the code at the very beginning
60 Most of these changes are self contained and the function presents itself
74 The aim is to define a so-called consistency model. It attempts to define
79 kpatch:  it uses kGraft's per-task consistency and syscall barrier
83 Patches are applied on a per-task basis, when the task is deemed safe to
108    a) Patching I/O-bound user tasks which are sleeping on an affected
111    b) Patching CPU-bound user tasks.  If the task is highly CPU-bound
146 transition, it shows -1.  Any tasks which are blocking the transition
174 ---------------------------------------------------------
180    for non-DWARF unwinders, also making sure there's a way for the stack
188    structures are in a well-defined state.
194    There the safe location must be carefully selected on a case-by-case
198    able to use the non-stack-checking parts of the consistency model:
215 samples/livepatch/livepatch-sample.c.
218 to replace. In addition, it defines some structures describing the
227 ------------------
239 Documentation/livepatch/module-elf-format.rst for more details.
243 -------------
248   - struct klp_func is defined for each patched function. It describes
265   - struct klp_object defines an array of patched functions (struct
275   - struct klp_patch defines an array of patched objects (struct
283     For more details on how the patch is applied on a per-task basis,
287 5. Livepatch life-cycle
299 ------------
312 -------------
348 --------------
360 See Documentation/livepatch/cumulative-patches.rst for more details.
364 --------------
377 to '0'. All the functions (struct klp_func) associated with the to-be-disabled
386 -------------
405 See Documentation/ABI/testing/sysfs-kernel-livepatch for more details.
413   - Only functions that can be traced could be patched.
423   - Livepatch works reliably only when the dynamic ftrace is located at
428     using -fentry gcc compiler option on x86_64.
437   - Kretprobes using the ftrace framework conflict with the patched
445   - Kprobes in the original function are ignored when the code is