Hi, Sorry for late response..
The speed calculation logic is from PTLsim era and little tricky because it counts cpu ticks between two points and uses 'ticks to second' conversion using the CPU frequency read from the /proc/cpuinfo. Now the issue with reading frequency from /proc/cpuinfo is that it always shows the 'current' frequency. Almost all of the CPUs have variable frequencies so if the frequency read was lower and if the simulation runs with higher frequency then you'll see this variation. I just discovered this bug it after reading your mail and digging through the code. To fix it we need to switch to better time functions rather than calculating it like this. - Avadh On Fri, Nov 11, 2011 at 7:52 AM, kuniors <[email protected]> wrote: > ** > Hello, > > A little weird that I finish 200 million instructions in 20 minutes but > the speed it says is 23000 insns / sec. > > Directly: 200 million / 23000 = 8659 sec. But in my real machine, only 20 > minutes past. > > The log file provides the simulation time that is around 8600 seconds. > > Confused a lot? What exactly the speef of ### insns / sec means? > > Thanks > > Kuniors > ================================= > kuniors2011-11-11 > > _______________________________________________ > http://www.marss86.org > Marss86-Devel mailing list > [email protected] > https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel > >
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
