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: gem5 use -F for interactive shell at end of boot restore

Browse Source 
fs_bitLITTLE: vmlinux.vexpress_gem5_v1.20170616 works without dtb
This commit is contained in:
Ciro Santilli
2018-05-01 11:46:52 +01:00
parent 37a4ff8070
commit 533fe808b6
1 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.adoc
View File

@@ -3667,7 +3667,7 @@ arch=aarch64
# Generate a checkpoint after Linux boots.
# The boot takes a while, be patient young Padawan.
printf 'm5 exit' > data/readfile
./run -a "$arch" -g -E 'm5 checkpoint;m5 readfile > a.sh;sh a.sh'
./run -a "$arch" -g -F 'm5 checkpoint;m5 readfile > a.sh;sh a.sh'
# Restore the checkpoint, and run the benchmark with parameter 1.000.
# We skip the boot completely, saving time!
@@ -3679,6 +3679,10 @@ printf 'm5 resetstats;dhrystone 1000;m5 exit' > data/readfile
printf 'm5 resetstats;dhrystone 10000;m5 exit' > data/readfile
./run -a "$arch" -g -- -r 1
./gem5-stat -a "$arch"
# Get an interactive shell at the end of the restore.
printf '' > data/readfile
./run -a "$arch" -g -- -r 1
....
These commands output the approximate number of CPU cycles it took Dhrystone to run.
@@ -4591,7 +4595,7 @@ Boot messages start at 5 minutes, boot finishes at 10 minutes and gives a shell.
`cat /proc/cpuinfo` shows 4 identical CPUs instead of 2 of two different types, likely because gem5 does not expose some informational register much like the caches: https://www.mail-archive.com/gem5-users@gem5.org/msg15426.html `config.ini` does show that the two big ones are `DerivO3CPU` and the small ones are `MinorCPU`.
TODO: why is the `--dtb` required despite `fs_bigLITTLE.py` having a DTB generation capability? Without it, nothing shows on terminal, and the simulation terminates with `simulate() limit reached @ 18446744073709551615`.
TODO: why is the `--dtb` required despite `fs_bigLITTLE.py` having a DTB generation capability? Without it, nothing shows on terminal, and the simulation terminates with `simulate() limit reached @ 18446744073709551615`. The magic `vmlinux.vexpress_gem5_v1.20170616` works however without a DTB.
== Insane action