Lines Matching full:functions

13        4.1. New functions
33 functions without a system reboot.
66 Functions are there for a reason. They take some input parameters, get or
70 Many fixes do not change the semantic of the modified functions. For
74 the same way to the rest of the system. In this case, the functions might
78 ordering of locking in multiple functions at the same time. Or a patch
80 all the relevant functions. In this case, the affected unit
82 the functions at the same time. Also the switch must happen only
86 The theory about how to apply functions a safe way is rather complex.
111    tasks.  If no affected functions are on the stack of a given task,
175 patch, which functions are (un)patched, and which functions the blocking tasks
230 The module includes a new implementation of functions that we want
239 4.1. New functions
242 New versions of functions are typically just copied from the original
248 The patch contains only functions that are really modified. But they
249 might want to access functions or data from the original source file
273     be used to disambiguate functions of the same name. This is not the
278   - struct klp_object defines an array of patched functions (struct
282     The structure helps to group and handle functions for each object
284     the patch itself and the relevant functions might be patched
291     This structure handles all patched functions consistently and eventually,
329 implementation of the patched functions at this stage.
331 First, the addresses of the patched functions are found according to their
332 names. The special relocations, mentioned in the section "New functions",
349     Note that functions might be patched multiple times. The ftrace handler
357     functions might be patched two times only during the transition period.
367 all the functions (struct klp_func) associated with the replaced
390 to '0'. All the functions (struct klp_func) associated with the to-be-disabled
401 Module removal is only safe when there are no users of functions provided
426   - Only functions that can be traced could be patched.
428     Livepatch is based on the dynamic ftrace. In particular, functions
431     potential mistake is prevented by marking the problematic functions
451     functions.