3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-29 04:54:27 +01:00
Code Issues Releases Wiki Activity

readme: aarch64 gem5 hpi slow: document gem5 update and cache size increase not working

Browse Source
This commit is contained in:
Ciro Santilli
2018-04-17 22:54:55 +01:00
parent cc6099dd6b
commit 96090a4c24
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
README.adoc
View File

@@ -4865,7 +4865,10 @@ TODO the following takes more than 1 hour to finish:
cmd ./run -a arm -E 'm5 exit' -g -- --caches --cpu-type=HPI 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`. But then I checked out there, run it, and kernel panics before any messages come out. Lol? 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? Things that did not happen:
* update gem5 to master 2a9573f5942b5416fb0570cf5cb6cdecba733392
* larger caches: `--l2cache --l1d_size=1024kB --l1i_size=1024kB --l2_size=1024kB --l3_size=1024kB`
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. 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.