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

getting started proofread

Browse Source
This commit is contained in:
Ciro Santilli 六四事件 法轮功
2019-02-07 00:00:00 +00:00
parent f70a935d3b
commit b13b140499
1 changed files with 3 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.adoc
View File

@@ -93,7 +93,7 @@ It is super easy to build for different <<cpu-architecture,CPU architectures>>,
./run --arch aarch64
....
To avoid typing `--arch aarch64` many times, you set the default arch as explained at: <<default-command-line-arguments>>
To avoid typing `--arch aarch64` many times, you can set the default arch as explained at: <<default-command-line-arguments>>
I now urge you to read the following sections which contain widely applicable information:
@@ -221,7 +221,7 @@ insmod /mnt/9p/out_rootfs_overlay/hello.ko
and the new `pr_info` message should now show on the terminal at the end of the boot.
This works because we have a <<9p>> mount there setup by default, which mounts the host directory that contains the Build outputs on the guest:
This works because we have a <<9p>> mount there setup by default, which mounts the host directory that contains the build outputs on the guest:
....
ls "$(./getvar out_rootfs_overlay_dir)"
@@ -320,12 +320,10 @@ Read the following sections for further introductory material:
This setup is like the <<qemu-buildroot-setup>>, but it uses link:http://gem5.org/[gem5] instead of QEMU as a system simulator.
QEMU tries to run as fast as possible and give correct results at the end, but it does not tell us how many CPU cycles it takes to do something, just the number of instructions it ran.
QEMU tries to run as fast as possible and give correct results at the end, but it does not tell us how many CPU cycles it takes to do something, just the number of instructions it ran. This kind of simulation is known as functional simulation.
The number of instructions executed is a very poor estimator of performance because in modern computers, a lot of time is spent waiting for memory requests rather than the instructions themselves.
This kind of simulation is known as functional simulation.
gem5 on the other hand, can simulate the system in more detail than QEMU, including:
* simplified CPU pipeline