gem5-bench-cache: allow bench without regenerating checkpoints

Print Dhrystone size on the output as well.
This commit is contained in:
Ciro Santilli
2018-04-05 11:57:25 +01:00
parent 8a68375b2e
commit 7d9102373d
2 changed files with 99 additions and 34 deletions

View File

@@ -2553,7 +2553,39 @@ So we take a performance measurement approach instead:
cat out/aarch64/gem5/bench-cache.txt
....
TODO: sort out HPI, and then paste results here, why the `--cpu-type=HPI` there always generates a `switch_cpu`, even if the original run was also on HPI?
which gives:
[options="header",cols="3*>"]
|===
|test size
|cache size
|cycle count
|1000
|1k
|52.432.956
|1000
|1M
|6.328.325
|10000
|1k
|141.637.834
|10000
|1M
|16.969.057
|100000
|1k
|1.034.500.724
|100000
|1M
|121.728.035
|===
===== gem5 memory latency
@@ -3027,7 +3059,7 @@ Internals:
* <<m5>> is a guest utility present inside the gem5 tree which we cross-compiled and installed into the guest
[[gem5-restore-new-scrip]]
===== gem5 checkpoint restore and run a different script
==== gem5 checkpoint restore and run a different script
You want to automate running several tests from a single pristine post-boot state.