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 arm possible good panics...

Browse Source
This commit is contained in:
Ciro Santilli
2018-04-17 21:33:24 +01:00
parent 991dd49748
commit ad6e311a8b
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.adoc
View File

@@ -4865,7 +4865,7 @@ TODO the following takes more than 1 hour to finish:
cmd ./run -a arm -E 'm5 exit' -g -- --caches --cpu-type=HPI
....
Why so long? I had previously documented on README 10 minutes at: 2eff007f7c3458be240c673c32bb33892a45d3a0 found with `git log` search for `10 minutes`, to be confirmed and bisected. We have a fixed kernel config for gem5, so the only two variables are the Linux kernel version, and the gem5 version.
Why so long? I had previously documented on README 10 minutes at: 2eff007f7c3458be240c673c32bb33892a45d3a0 found with `git log` search for `10 minutes`. But then I checked out there, run it, and kernel panics before any messages come out. Lol?
One methodology problem is that some gem5 and QEMU were run with different kernel configs, due to <<gem5-qemu-config>>. This could have been improved if we normalized by instruction counts, but to do that we would have to enable tracing which makes QEMU run much slower.