Lines Matching refs:loader

37 exists in the module loader, so this former approach produced redundant
39 loader can already do, livepatch leverages existing code in the module
40 loader to perform the all the arch-specific relocation work. Specifically,
41 livepatch reuses the apply_relocate_add() function in the module loader to
60 since the kernel module loader cannot resolve them and will therefore
88 used by the kernel module loader to identify livepatch modules.
138 loader recognizes this flag and will avoid applying those relocation sections
140 so that the module loader doesn't discard them on module load (i.e. they will
205 objects, whose addresses cannot be resolved by the module loader (because
206 they are local or unexported global syms). Since the module loader only
218 loader can identify and ignore them. Livepatch modules keep these symbols
254 that the module loader can identify them and not attempt to resolve them.
314 livepatch modules and is made accessible by the module loader through
316 this struct is filled in by the module loader. Its fields are documented below: