Check how that function is actually used. I think it just figures out when the next cycle boundary is from the given tick, and that's only necessary in certain circumstances. Most of the time you can just add the period to the current tick. If you want to create a periodic event, it would be best to actually create a new event that does what you want rather than trying to piggyback on something else.
Gabe On 02/23/11 12:20, Anubhav Kumar Singh wrote: > Hi, > > I was trying to generate a periodic call to a certain function in M5. > > For this i tried to modify src/cpu/base.cc > > I figured the follwoing function would get called regularly every cycle : > > Tick BaseCPU::nextCycle(Tick begin_tick) > > So I added a cprintf line to check if its indeed the case. > > However I get the following output in the HelloWorld test script: > > M5 compiled Feb 23 2011 14:43:52 > M5 revision Unknown > M5 started Feb 23 2011 14:44:12 > M5 executing on tornado > command line: ./build/ALPHA_SE/m5.fast configs/example/se.py > Global frequency set at 1000000000000 ticks per second > 0: system.remote_gdb.listener: listening for remote gdb on port 7000 > Anubhav > **** REAL SIMULATION **** > info: Entering event queue @ 0. Starting simulation... > info: Increasing stack size by one page. > Hello world! > hack: be nice to actually delete the event here > Exiting @ cycle 3260000 because target called exit() > > I have highlighted the modified printing part. As can be seen, this > function is only getting called apparently before the simulation begins. > > What am I doing wrong here? Do I need to use some other function than > this for regular call? > > -- > Anubhav Kumar Singh > Doctoral Student > Department of Computer & > Information Science & Engineering > University of Florida > > > _______________________________________________ > 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
