github-mirror/lkmpg
github-mirror/lkmpg
2
0
Fork 0
mirror of https://github.com/sysprog21/lkmpg.git synced 2025-03-13 14:05:10 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Refine wording on module loading

Browse Source 
Close #134
This commit is contained in:
Jim Huang 2022-03-16 14:32:08 +08:00
parent 356723c824
commit 19521bc60a
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
lkmpg.tex
View File

@ -704,7 +704,7 @@ You use these library functions which are provided by the standard C library, li
The definitions for these functions do not actually enter your program until the linking stage, which insures that the code (for \cpp|printf()| for example) is available, and fixes the call instruction to point to that code.
Kernel modules are different here, too. In the hello world example, you might have noticed that we used a function, \cpp|pr_info()| but did not include a standard I/O library.
That is because modules are object files whose symbols get resolved upon \sh|insmod|'ing.
That is because modules are object files whose symbols get resolved upon running \sh|insmod| or \sh|modprobe|.
The definition for the symbols comes from the kernel itself; the only external functions you can use are the ones provided by the kernel.
If you're curious about what symbols have been exported by your kernel, take a look at \verb|/proc/kallsyms|.