Lines Matching +full:waking +full:- +full:up

15     5. Livepatch life-cycle
30 heavy load during peak usage. In addition to keeping systems up and running,
43   - The kernel probes are the most generic. The code can be redirected by
46   - The function tracer calls the code from a predefined location that is
48     compiler using the '-pg' gcc option.
50   - Livepatching typically needs to redirect the code at the very beginning
87 The aim is to define a so-called consistency model. It attempts to define
92 kpatch:  it uses kGraft's per-task consistency and syscall barrier
96 Patches are applied on a per-task basis, when the task is deemed safe to
121    a) Patching I/O-bound user tasks which are sleeping on an affected
124    b) Patching CPU-bound user tasks.  If the task is highly CPU-bound
138 especially applies to kthreads. They may not be woken up and would need
141 Unless we can come up with another way to patch kthreads, architectures
159 transition, it shows -1.  Any tasks which are blocking the transition
164 interrupted or woken up, and forced to change their patched state. The fake
187 ---------------------------------------------------------
193    for non-DWARF unwinders, also making sure there's a way for the stack
201    structures are in a well-defined state.
207    There the safe location must be carefully selected on a case-by-case
211    able to use the non-stack-checking parts of the consistency model:
219    user tasks and waking kthreads to patch them.  But it could still be
228 samples/livepatch/livepatch-sample.c.
234 module is loaded. Also there is code that cleans up before the
240 ------------------
252 Documentation/livepatch/module-elf-format.rst for more details.
256 -------------
261   - struct klp_func is defined for each patched function. It describes
278   - struct klp_object defines an array of patched functions (struct
288   - struct klp_patch defines an array of patched objects (struct
296     For more details on how the patch is applied on a per-task basis,
300 5. Livepatch life-cycle
312 ------------
325 -------------
361 --------------
373 See Documentation/livepatch/cumulative-patches.rst for more details.
377 --------------
390 to '0'. All the functions (struct klp_func) associated with the to-be-disabled
399 -------------
418 See Documentation/ABI/testing/sysfs-kernel-livepatch for more details.
426   - Only functions that can be traced could be patched.
430     patched. Otherwise, the code would end up in an infinite loop. A
436   - Livepatch works reliably only when the dynamic ftrace is located at
441     using -fentry gcc compiler option on x86_64.
450   - Kretprobes using the ftrace framework conflict with the patched
458   - Kprobes in the original function are ignored when the code is