Lines Matching refs:patched

85 transition state where tasks are converging to the patched state.
88 the patched state to the unpatched state.
90 An interrupt handler inherits the patched state of the task it
92 patched state of the parent.
99    the task is patched.  In most cases this will patch most or all of
110       force it to exit the kernel and be patched.
112       then it will get patched the next time it gets interrupted by an
117    allows them to be patched before the CPU enters the idle state.
145 unpatched and 1 to indicate it's patched.  Otherwise, if no patch is in
148 patched state. This may be harmful to the system though. Sending a fake signal
151 interrupted or woken up, and forced to change their patched state. The fake
156 TIF_PATCH_PENDING flag of all tasks and thus forces the tasks to the patched
162 patch, which functions are (un)patched, and which functions the blocking tasks
248   - struct klp_func is defined for each patched function. It describes
265   - struct klp_object defines an array of patched functions (struct
270     together. Note that patched modules might be loaded later than
271     the patch itself and the relevant functions might be patched
275   - struct klp_patch defines an array of patched objects (struct
278     This structure handles all patched functions consistently and eventually,
279     synchronously. The whole patch is applied only when all patched
316 implementation of the patched functions at this stage.
318 First, the addresses of the patched functions are found according to their
325 to the patched state. If an original function is patched for the first
331 Finally, once all tasks have been patched, the 'transition' value changes
336     Note that functions might be patched multiple times. The ftrace handler
344     functions might be patched two times only during the transition period.
391 to a new patch state (patched/unpatched) without being forced it is
413   - Only functions that can be traced could be patched.
417     patched. Otherwise, the code would end up in an infinite loop. A
437   - Kretprobes using the ftrace framework conflict with the patched