3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-27 12:04:27 +01:00
Code Issues Releases Wiki Activity

readme: getting started tidbits

Browse Source
This commit is contained in:
Ciro Santilli
2018-09-14 07:59:04 +01:00
parent cb8a2f843c
commit bcece8b335
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.adoc
View File

@@ -27,11 +27,11 @@ System simulators are cool compared to real hardware because they are:
The current components we focus the most on are: The current components we focus the most on are:
* Linux kernel and Linux kernel modules * <<linux-kernel>> and Linux kernel modules
* full systems emulators, currently <<qemu-buildroot-setup,qemu>> and <<gem5-buildroot-setup,gem5>> * full systems emulators, currently <<qemu-buildroot-setup,qemu>> and <<gem5-buildroot-setup,gem5>>
* <<buildroot>>. We use and therefore document, a large part of its feature set. * <<buildroot>>. We use and therefore document, a large part of its feature set.
The following components are not covered, but it shouldn't be hard to do: The following components are not covered, but they would also benefit from this setup, and it shouldn't be hard to add them:
* C standard libraries * C standard libraries
* compilers. Project idea: add a new instruction to x86, then hack up GCC to actually use it, and make a C program that generates it. * compilers. Project idea: add a new instruction to x86, then hack up GCC to actually use it, and make a C program that generates it.
@@ -53,7 +53,7 @@ If you don't know which one to go for, start with <<qemu-buildroot-setup>>.
The trade-offs are basically a balance between: The trade-offs are basically a balance between:
* speed ans size; how long and how much disk space do the build and run take? * speed ans size: how long and how much disk space do the build and run take?
* visibility: can you GDB step debug everything and read source code? * visibility: can you GDB step debug everything and read source code?
* modifiability: can you modify the source code and rebuild a modified version? * modifiability: can you modify the source code and rebuild a modified version?
* portability: does it work on a Windows host? Could it ever? * portability: does it work on a Windows host? Could it ever?
@@ -3454,7 +3454,7 @@ This likely comes from the ifdef split at `init/main.c`:
=== Linux kernel entry point === Linux kernel entry point
`start_kernel` is a good definition of it: ttps://stackoverflow.com/questions/18266063/does-kernel-have-main-function/33422401#33422401 `start_kernel` is a good definition of it: https://stackoverflow.com/questions/18266063/does-kernel-have-main-function/33422401#33422401
=== Kernel module APIs === Kernel module APIs