Lines Matching full:loader

18 exists in the module loader, so this former approach produced redundant
20 loader can already do, livepatch leverages existing code in the module
21 loader to perform the all the arch-specific relocation work. Specifically,
22 livepatch reuses the apply_relocate_add() function in the module loader to
41 since the kernel module loader cannot resolve them and will therefore
64 used by the kernel module loader to identify livepatch modules.
112 loader recognizes this flag and will avoid applying those relocation sections
114 so that the module loader doesn't discard them on module load (i.e. they will
192 objects, whose addresses cannot be resolved by the module loader (because
193 they are local or unexported global syms). Since the module loader only
205 loader can identify and ignore them. Livepatch modules keep these symbols
238 that the module loader can identify them and not attempt to resolve them.
300 livepatch modules and is made accessible by the module loader through
302 loads, this struct is filled in by the module loader.