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

readme: fix --gem5 references

Browse Source
This commit is contained in:
Ciro Santilli
2019-01-22 00:00:00 +00:00
committed by Ciro Santilli 六四事件 法轮功
parent 7c7ac82a6b
commit 8499df9879
2 changed files with 13 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
README.adoc
View File

@@ -84,7 +84,7 @@ See also: <<quit-qemu-from-text-mode>>.
All available modules can be found in the link:kernel_modules[] directory.
It is super easy to build for different CPU architectures, just use the `--arch` option:
It is super easy to build for different <<cpu-architecture,CPU architectures>>, just use the `--arch` option:
....
./build --arch aarch64 --download-dependencies qemu-buildroot
@@ -93,8 +93,6 @@ It is super easy to build for different CPU architectures, just use the `--arch`
To avoid typing `--arch aarch64` many times, you set the default arch as explained at: <<default-command-line-arguments>>
See also: <<cpu-architecture,CPU architectures>>.
I now urge you to read the following sections which contain widely applicable information:
* <<run-command-after-boot>>
@@ -336,7 +334,7 @@ See <<gem5-vs-qemu>> for a more thorough comparison.
==== gem5 Buildroot setup getting started
For the most part, if you just add the `--gem5` option or `*-gem5` suffix to all commands and everything should magically work.
For the most part, if you just add the `--emulator gem5` option or `*-gem5` suffix to all commands and everything should magically work.
If you haven't built Buildroot yet for <<qemu-buildroot-setup>>, you can build from the beginning with:
@@ -792,9 +790,15 @@ and then <<qemu-buildroot-setup,as usual>> open a shell with:
./gem5-shell
....
Or as usualy, <<tmux>> users can do both in one go with:
....
./run --arch aarch64 --baremetal interactive/prompt --emulator gem5 --tmux
....
TODO: the carriage returns are a bit different than in QEMU, see: <<gem5-baremetal-carriage-return>>.
Note that `./build-baremetal` requires the `--gem5` option, and generates separate executable images for both, as can be seen from:
Note that `./build-baremetal` requires the `--emulator gem5` option, and generates separate executable images for both, as can be seen from:
....
echo "$(./getvar --arch aarch64 --baremetal interactive/prompt image)"
@@ -804,7 +808,7 @@ echo "$(./getvar --arch aarch64 --baremetal interactive/prompt --emulator gem5 i
This is unlike the Linux kernel that has a single image for both QEMU and gem5:
....
echo "$(./getvar --arch aarch64 image)"
echo "$(./getvar --arch aarch64 --emulator qemu image)"
echo "$(./getvar --arch aarch64 --emulator gem5 image)"
....

6
bench-boot
View File

@@ -54,7 +54,7 @@ newline
if [ "$test_size" -ge 2 ]; then
bench "${arch} --eval '/poweroff.out' --trace exec_tb"
qemu_insts "$arch"
bench "$arch --eval 'm5 exit' --gem5"
bench "$arch --eval 'm5 exit' --emulator gem5"
gem5_insts "$arch"
fi
#bench "$arch --eval 'm5 exit' --emulator gem5 -- --cpu-type=DerivO3CPU ${caches}"
@@ -65,7 +65,7 @@ bench "$arch --eval '/poweroff.out'"
if [ "$test_size" -ge 2 ]; then
bench "$arch --eval '/poweroff.out' --trace exec_tb"
qemu_insts "$arch"
bench "$arch --eval 'm5 exit' --gem5"
bench "$arch --eval 'm5 exit' --emulator gem5"
gem5_insts "$arch"
fi
if [ "$test_size" -ge 3 ]; then
@@ -79,7 +79,7 @@ newline
if [ "$test_size" -ge 2 ]; then
bench "$arch --eval '/poweroff.out' --trace exec_tb"
qemu_insts "$arch"
bench "$arch --eval 'm5 exit' --gem5"
bench "$arch --eval 'm5 exit' --emulator gem5"
gem5_insts "$arch"
fi
if [ "$test_size" -ge 3 ]; then