sim_freq is the frequency of the simulator itself, or in other words, is a measure of the minimal amount of time that has meaning in the simulator. In m5, this is a pico second which gives the 1 THz frequency you're seeing. I'm not sure whether sim_seconds is what you should expect, but it seems like it's being calculated correctly. One second of simulated time can take a LONG time in actual time depending on many factors, so you may need to reconsider what seems reasonable.
Gabe Julian Bui wrote: > Hi all, > > I've observed a strange thing in m5stats.txt that I can't explain. I > have I've looked on google and the m5 website for an explanation of what > we're seeing and haven't found it. > > The sim_freq of our m5stats.txt file says 1,000,000,000,000. If I'm > interpreting that correctly, that's saying that our system was running > at 1Terahertz. Is that correct? We specified our CPU and bus > frequencies to be 1GHz so we would have expected it to say > 1,000,000,000. Why is it off by a factor of 1000? It does not make > sense to me. > > Furthermore, our sim_ticks says 79163591000. Dividing our sim_ticks by > our sim_freq we get our sim_seconds = .079164 seconds which is what the > m5stats.txt file says. This seems too quick for the large amount of > work we are doing. If we instead divide by 1GHz we get 79.164 seconds > which seems more correct. It seems that we are missing some > understanding about the simulator. Could someone please explain what's > going on? > > Any help is greatly appreciated. > > Thanks, > Julian > > > ------------------------------------------------------------------------ > > _______________________________________________ > m5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users _______________________________________________ m5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
