Hi all, I'm a little confused with this problem now. I think the PARSEC script did not run supported by another evidence is that I tried to dump stats every n ticks by modifying .rcS file from: cd /parsec/install/bin /sbin/m5 switchcpu /sbin/m5 dumpstats /sbin/m5 resetstats ./blackscholes 16 /parsec/install/inputs/blackscholes/in_4K.txt /parsec/install\ /inputs/blackscholes/prices.txt echo "Done :D" /sbin/m5 exit /sbin/m5 exit
to: cd /parsec/install/bin /sbin/m5 switchcpu /sbin/m5 dumpstats 10 100000 /sbin/m5 resetstats ./blackscholes 16 /parsec/install/inputs/blackscholes/in_4K.txt /parsec/install\ /inputs/blackscholes/prices.txt echo "Done :D" /sbin/m5 exit /sbin/m5 exit with command ./build/ALPHA_MESI_CMP_directory/m5.opt ./configs/example/fs.py -n 16 --script=blackscholes_16c_simsmall.rcS -I 10000000 --cpu-type=detailed --caches The stats.txt file does not have any change. What I hoped is to have multiple copies of stats in stats.txt file because system will dump stats every 100000 ticks. But when I tried to run command: ./build/ALPHA_MESI_CMP_directory/m5.opt ./configs/example/fs.py --script=blackscholes_16c_simsmall.rcS after some time it exits with "Exiting @ tick 1892710156000 because switchcpu", that means script works. So I don't know how to explain this and how can I get PARSEC run with stats dumped every certain ticks. Regards, -- Xi Chen
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users