Hello, I am trying to run gem5 in SE mode with simpoints enabled. I am able to generate simpoints for some spec2006 benchmarks. I can see that after generating the simpoints, we have two options to simulate the simpoints using detailed cpu.
(1) To do fastfwd using simpoint-mode=fastfwd - This will fast forward the non-simpoint regions using atomic cpu and then switch to detailed cpu in simpoint regions. Ex: ./build/ARM/gem5.opt configs/pharm/se2.py --cfg=configs/pharm/nehalem. cfg --cmd=../tests/libquantum_base.armv7a-O3-vfpv3d16-vect -o "15 2" --simpoint-mode=fastfwd --simpoint-interval=1000000 --simpoint-points=simpoints (2) To simulate a specific checkpoint using simpoint-mode=checkpoint. ./build/ARM/gem5.opt configs/pharm/se2.py --cfg=configs/pharm/nehalem. cfg --cmd=../tests/libquantum_base.armv7a-O3-vfpv3d16-vect -o "15 2" --simpoint-mode=checkpoint --simpoint-interval=1000000 --simpoint-points=simpoints --checkpoint-dir=ckpt --checkpoint-num=1 I am using classical caches in SE mode. Would like to know if using the corresponding commands in both the cases would warmup the caches automatically or do I need to mention some flag explicitly ? Regards, Jagadish.
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
