I think you're going to have to debug a little bit and see if the cache is responding and that isn't rescheduling the tick event, or if there isn't a response and why. Ali
On May 12, 2012, at 9:19 AM, Yuval H. Nacson wrote: > Hello, > > I'm new to gem5. > I'm trying to run 2 threads in ALPHA SE mode. The simulation runs for a very > short while and I get the following message: > Exiting @ tick 9223372036854775807 because simulate() limit reached. > Turning on the debug flags I see that on the first data cache miss the > simulator suspends the active thread and activates the next ready thread. > When both of my threads are suspended the CPU "goes to sleep" and never > awaken again. > I dug into the code a bit and my guess is that the cache never signals a > suspended thread that he completed the memory access and the suspended thread > never checks it. > > Is there any solution for this problem? Or any suggestion for how should I > fix it? > > Thanks, > Yuval. > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
