Lines Matching full:functions

20 functions without a system reboot.
53 Functions are there for a reason. They take some input parameters, acquire or
57 Many fixes do not change the semantic of the modified functions. For
61 the same way to the rest of the system. In this case, the functions might
65 ordering of locking in multiple functions at the same time. Or a patch
67 all the relevant functions. In this case, the affected unit
69 the functions at the same time. Also the switch must happen only
73 The theory about how to apply functions a safe way is rather complex.
98    tasks.  If no affected functions are on the stack of a given task,
162 patch, which functions are (un)patched, and which functions the blocking tasks
217 The module includes a new implementation of functions that we want
226 4.1. New functions
229 New versions of functions are typically just copied from the original
235 The patch contains only functions that are really modified. But they
236 might want to access functions or data from the original source file
260     be used to disambiguate functions of the same name. This is not the
265   - struct klp_object defines an array of patched functions (struct
269     The structure helps to group and handle functions for each object
271     the patch itself and the relevant functions might be patched
278     This structure handles all patched functions consistently and eventually,
316 implementation of the patched functions at this stage.
318 First, the addresses of the patched functions are found according to their
319 names. The special relocations, mentioned in the section "New functions",
336     Note that functions might be patched multiple times. The ftrace handler
344     functions might be patched two times only during the transition period.
354 all the functions (struct klp_func) associated with the replaced
377 to '0'. All the functions (struct klp_func) associated with the to-be-disabled
388 Module removal is only safe when there are no users of functions provided
413   - Only functions that can be traced could be patched.
415     Livepatch is based on the dynamic ftrace. In particular, functions
418     potential mistake is prevented by marking the problematic functions
438     functions.