Umm, it's a simulator, and you requested the most detailed simulation mode (DerivO3CPU). I expect slowdown factors of *at least* 1000 with such a mode. That you are seeing perhaps 4000-5000 does not surprise me all that much. The simulator has to do a lot of work for each simulated instruction.
If you just want hit/miss statistics, a simpler cpu model might serve your purpose. The simplest that might do it is AtomicSimpleCPU - it certainly maintains a model of the cache; I am less certain about branch prediction. Tools other gem5 may get you this kind of result faster - maybe some of the valgrind tools, for example. Others might be able to confirm or argue against my sense of the slowdown factor (which I sometimes call the *time dilation* of simulation). HTH - Eliot Moss _______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
