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

readme: some minor fixes

Browse Source
This commit is contained in:
Ciro Santilli 六四事件 法轮功
2019-02-20 00:00:02 +00:00
parent 7c2a9c0e9c
commit 9d69ec26a6
1 changed files with 7 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
README.adoc
View File

@@ -211,7 +211,7 @@ and rebuild with:
./build-modules
....
Now there are two way to test it out, the fast way, and the safe way.
Now there are two ways to test it out: the fast way, and the safe way.
The fast way is, without quitting or rebooting QEMU, just directly re-insert the module with:
@@ -231,7 +231,7 @@ The fast method is slightly risky because your previously insmodded buggy kernel
Such failures are however unlikely, and you should be fine if you don't see anything weird happening.
The safe way, is to fist quit QEMU, rebuild the modules, put them in the root filesystem, and then reboot:
The safe way, is to fist <<rebuild-buildroot-while-running,quit QEMU>>, rebuild the modules, put them in the root filesystem, and then reboot:
....
./build-modules
@@ -4436,7 +4436,7 @@ although this can be useful when someone gives you a random image.
By default, link:build-linux[] generates a `.config` that is a mixture of:
* a base config extracted from Buildroot's minimal per machine `.config`, which has the minimal options needed to boot: <<about-buildroots-kernel-configs>>
* a base config extracted from Buildroot's minimal per machine `.config`, which has the minimal options needed to boot: <<about-buildroot-s-kernel-configs>>
* small overlays put top of that
To find out which kernel configs are being used exactly, simply run:
@@ -11414,7 +11414,7 @@ So we see in both cases that the `svc` is done, then an exception happens, and t
The vector table format is described on <<armarm8>> Table D1-7 "Vector offsets from vector table base address".
A good representation of the format of the vector table can also be found at <<programmers-guide-for-armv8-a>> Table 10-2 "Vector table offsets from vector table base address".
A good representation of the format of the vector table can also be found at <<programmer-s-guide-for-armv8-a>> Table 10-2 "Vector table offsets from vector table base address".
The first part of the table contains:
@@ -12525,16 +12525,14 @@ We have link:https://buildroot.org/downloads/manual/manual.html#ccache[enabled c
* absolute paths are used and GDB can find source files
* but builds are not reused across separated LKMC directories
=== Rebuild while running
=== Rebuild buildroot while running
Not possible because
It is not possible to rebuild the root filesystem while running QEMU because QEMU holds the file qcow2 file:
....
Text file busy
error while converting qcow2: Failed to get "write" lock
....
openat(AT_FDCWD, "sleep.out", O_WRONLY) = -1 ETXTBSY ()
=== Simultaneous runs
When doing long simulations sweeping across multiple system parameters, it becomes fundamental to do multiple simulations in parallel.