> Can you elaborate on last item - Consolidate under a single stats > infrastructure and stats output file. Ah, that's a good one. To put it simply, there are two different systems for generating stats. The M5 system and the Ruby system. M5's system is pretty structured and uses the m5 "stats package". Ruby's system is basically a bunch of print statements. The former is nice because it leads to more easily parsed output files and can easily support features like resetting all stats, or outputting stats to formats other than text (there's a mysql backend for the M5 stats). What this basically means is going through all of the Ruby objects and creating M5 style stats to replace the existing ruby ones. It is something that is pretty easy to do, but is not purely mechanical.
As a note to others, I am actually resurrecting output to non-text feature right now because the text files are becoming a problem for me (too big). I'm doing it a bit differently now though as I am redoing all of the stats output stuff in python instead of C++, so it will be easy to just use python libraries to output stats in say XML or Berkeley db or whatever. (I'm using a lot of existing code from util/stats that was originally for the mysql stuff, but never really polished.) Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
