From 96090a4c245afa83b0a850f74948a262a4a3325d Mon Sep 17 00:00:00 2001 From: Ciro Santilli Date: Tue, 17 Apr 2018 22:54:55 +0100 Subject: [PATCH] readme: aarch64 gem5 hpi slow: document gem5 update and cache size increase not working --- README.adoc | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.adoc b/README.adoc index 4447740..da290c4 100644 --- a/README.adoc +++ b/README.adoc @@ -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 .... -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 <>. 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.