On Jul 16, 2013, at 11:03 AM, Fulya Kaplan <[email protected]> wrote: > Hi all, > I am running Parsec on X86 and trying to use dumpresetstats periodically. > Since I am using the precompiled Parsec binaries, I use the m5op > dumpresetstats for this purpose. I am using the command line: > > ../build/X86/gem5.opt --outdir=../RUNS/2core_fastfwd_dumpstats/m5out_canneal > ../configs/example/fs.py > --disk-image=/home/fkaplan/Stravinsky/gem5/full_system/disks/x86root-parsec.img > > --kernel=/home/fkaplan/Stravinsky/gem5/full_system/binaries/x86_64-vmlinux-2.6.28.4-smp > --script=./canneal_2c_simmedium.rcS -n 2 --cpu-type=detailed --caches > --l2cache --num-l2caches=2 --l1d_size=32kB --l1i_size=32kB --l1d_assoc=8 > --l1i_assoc=2 --l2_size=512kB --l2_assoc=16 --fast-forward=2500000000 > My .rcS script looks like: > > #!/bin/sh > # File to run the canneal benchmark > cd /parsec/install/bin > #/sbin/m5 switchcpu > #/sbin/m5 dumpstats > #/sbin/m5 resetstats > /sbin/m5 dumpresetstats 10 100000000000 > ./canneal 2 15000 2000 /parsec/install/inputs/canneal/200000.nets 64 > echo "Done :D" > /sbin/m5 exit > /sbin/m5 exit > However, when i check the stats.txt file, i see only 1 set of stats. I chose > the period of dumpresetstats high enough so that it will correspond to > ~millions of instructions range. Could you help me on what could be the > problem? Do i need to modify any other files than .rcS file? > Best, > Fulya > > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
No you shouldn't need to modify anything else. Perhaps the dumpreststats m5 op isn't working. Could you put a DPRINTFN() in the src/sim/pseudo_insts.cc file where the dumpresetstats call is and make sure the parameters it's getting are correct? Ali _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
