Lines Matching refs:loader

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