Conceptually yes. There is usually an event or something an event causes which tells gem5 to exit, like the last thread of a process exiting, or the m5 utility running inside a full system simulation telling the simulator it wants to exit. That will make gem5 return to the config script where it will usually report that the simulation ended and exit the simulator, but it can technically go back in and keep processing events. If the simulator really runs out of events to process all together, time will conceptually advance to the max time and the simulator will exit.
On Mon, Jun 15, 2020 at 8:42 PM Taiyu Zhou via gem5-users < [email protected]> wrote: > Thank you so much,Gabe. So the total time gem5 runs is depending on the > final event? > > _______________________________________________ > gem5-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s >
_______________________________________________ gem5-users mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
