There are resetstats and dumpstats magic instructions that are used to dump a separate dump for each ROI. Some programs consist of many ROIs and of course many uninteresting regions. So for those programs calling dumpstats several times would result in a really long stats file. A large stats file is not a problem by itself. The problem is that a parser (in my case a perl script) should go through the stats and extract (and sometimes combine) data from multiple dumps to generate a unified single statistic information for the entire program (I am interested in all ROIs together not just each ROI seperately). In these kinds of programs it would be really nice to have the capability to disable stats for all modules (including caches) when the program enters an uninteresting region and then enable it again for ROI. I took a look at stats source file and saw how reset() is implemented. I am going to give it a shot and implement some kind of stats disable and enable feature. I think a possible approach could be to save stats when they are disabled and restore them when they are enabled. Any pointers/suggestions on this would be appreciated.
Thanks, Amin
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
