Hi, you can make a checkpoint at a billion cycle and then restore the simulation at this point. I would say that the debug-flag cannot give us the whole trace because as you can see from the output, it shows data every several ticks. Maybe you can get the trace directly from the source code.
Regards Xiangyang On Tue, Oct 15, 2013 at 3:57 PM, Abhishek Deshpande <[email protected]>wrote: > Hi, > > I want to trace cache log to analyse read and write accesses w.r.t. tick. > I need to start simulation to dump trace file after a billion cycles so > that misses due to cache initialization will not be present in results. > > Can you please help me to do so. Any other switches I need to add to my > command line. > > I am using following command: > build/ALPHA/gem5.opt --quiet --outdir=result --trace-file=trace_radix.out > --debug-flags=Cache configs/example/se.py --cpu-type=detailed --num-cpus=1 > --cpu-clock=2.0GHz --caches --l2cache --num-l2caches=1 --l1d_size=32kB > --l1d_assoc=8 --l1i_size=32kB --l1i_assoc=4 --l2_size=256kB --l2_assoc=8 > --abs-max-tick=500000000000 --output=radix_output -c > benchmark/v1-splash-alpha/splash2/codes/kernels/radix/RADIX > > Thank you for your help and support. > > Regards, > Abhishek > > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
