bench-boot: add updated benchmark

This commit is contained in:
Ciro Santilli 六四事件 法轮功
2018-11-04 00:00:01 +00:00
parent 8fb9db3931
commit b5b1245f82

View File

@@ -10500,49 +10500,74 @@ Run all kernel boot benchmarks for one arch:
cat "$(./getvar bench_boot)" cat "$(./getvar bench_boot)"
.... ....
Sample results at 2bddcc2891b7e5ac38c10d509bdfc1c8fe347b94: Sample results at 8fb9db39316d43a6dbd571e04dd46ae73915027f:
.... ....
cmd ./run --arch x86_64 --eval '/poweroff.out' cmd ./run --arch x86_64 --eval '/poweroff.out'
time 7.46 time 8.25
exit_status 0 exit_status 0
cmd ./run --arch x86_64 --eval '/poweroff.out' --kvm cmd ./run --arch x86_64 --eval '/poweroff.out' --kvm
time 7.61 time 1.22
exit_status 0 exit_status 0
cmd ./run --arch x86_64 --eval '/poweroff.out' --trace exec_tb cmd ./run --arch x86_64 --eval '/poweroff.out' --trace exec_tb
time 8.04 time 8.83
exit_status 0 exit_status 0
instructions 1665023 instructions 2244297
cmd ./run --arch x86_64 --eval 'm5 exit' --gem5 cmd ./run --arch x86_64 --eval 'm5 exit' --gem5
time 254.32 time 213.39
exit_status 0 exit_status 0
instructions 380799337 instructions 318486337
cmd ./run --arch arm --eval '/poweroff.out' cmd ./run --arch arm --eval '/poweroff.out'
time 5.56 time 6.62
exit_status 0 exit_status 0
cmd ./run --arch arm --eval '/poweroff.out' --trace exec_tb cmd ./run --arch arm --eval '/poweroff.out' --trace exec_tb
time 5.78 time 6.90
exit_status 0 exit_status 0
instructions 742319 instructions 776374
cmd ./run --arch arm --eval 'm5 exit' --gem5
time 118.46
exit_status 0
instructions 153023392
cmd ./run --arch arm --eval 'm5 exit' --gem5 -- --cpu-type=HPI --caches --l2cache --l1d_size=1024kB --l1i_size=1024kB --l2_size=1024kB --l3_size=1024kB
time 2250.40
exit_status 0
instructions 151981914
cmd ./run --arch aarch64 --eval '/poweroff.out' cmd ./run --arch aarch64 --eval '/poweroff.out'
time 4.85 time 4.94
exit_status 0 exit_status 0
cmd ./run --arch aarch64 --eval '/poweroff.out' --trace exec_tb cmd ./run --arch aarch64 --eval '/poweroff.out' --trace exec_tb
time 4.91 time 5.04
exit_status 0 exit_status 0
instructions 245471 instructions 233162
cmd ./run --arch aarch64 --eval 'm5 exit' --gem5 cmd ./run --arch aarch64 --eval 'm5 exit' --gem5
time 68.71 time 70.89
exit_status 0 exit_status 0
instructions 120555566 instructions 124346081
cmd ./run --arch aarch64 --eval 'm5 exit' --gem5 -- --cpu-type=HPI --caches --l2cache --l1d_size=1024kB --l1i_size=1024kB --l2_size=1024kB --l3_size=1024kB
time 381.86
exit_status 0
instructions 124564620
cmd ./run --arch aarch64 --eval 'm5 exit' --gem5 --gem5-build-type fast
time 58.00
exit_status 0
instructions 124346081
cmd ./run --arch aarch64 --eval 'm5 exit' --gem5 --gem5-build-type debug
time 1022.03
exit_status 0
instructions 124346081
.... ....
TODO: aarch64 gem5 and QEMU use the same kernel, so why is the gem5 instruction count so much much higher? TODO: aarch64 gem5 and QEMU use the same kernel, so why is the gem5 instruction count so much much higher?