Lines Matching full:loader

24 exists in the module loader, so this former approach produced redundant
26 loader can already do, livepatch leverages existing code in the module
27 loader to perform the all the arch-specific relocation work. Specifically,
28 livepatch reuses the apply_relocate_add() function in the module loader to
47 since the kernel module loader cannot resolve them and will therefore
70 used by the kernel module loader to identify livepatch modules.
118 loader recognizes this flag and will avoid applying those relocation sections
120 so that the module loader doesn't discard them on module load (i.e. they will
198 objects, whose addresses cannot be resolved by the module loader (because
199 they are local or unexported global syms). Since the module loader only
211 loader can identify and ignore them. Livepatch modules keep these symbols
244 that the module loader can identify them and not attempt to resolve them.
306 livepatch modules and is made accessible by the module loader through
308 this struct is filled in by the module loader. Its fields are documented below::