bench-boot and trace-boot: make keys more pareseable and meaningful

This commit is contained in:
Ciro Santilli
2018-04-07 18:31:55 +01:00
parent 5285af405e
commit 10348beeff
2 changed files with 5 additions and 6 deletions

View File

@@ -7,7 +7,7 @@ bench() (
env time --append -f 'time %e' --output="$results_file" ./eeval "./run -a $1" "$results_file"
)
insts() (
{ printf 'insts '; ./gem5-stat -a "$1" sim_insts; } >> "$results_file"
{ printf 'instructions '; ./gem5-stat -a "$1" sim_insts; } >> "$results_file"
)
rm -f "${results_file}"
@@ -16,8 +16,7 @@ arch=arm
#bench "$arch -E '/poweroff.out'"
bench "$arch -E 'm5 exit' -g"
insts "$arch"
# TODO didn't finish after 20 minutes? Stuck at:
# ftrace: allocating 28852 entries in 85 pages
# TODO takes more than 1 hours to finish. Why so long?
#bench "$arch -E 'm5 exit' -g -- --caches --cpu-type=HPI"
#insts "$arch"