Can someone explain the trick behind "RubySystem::memWriteback()" function? More specifically, why all events first dequeued from ruby's queue and then simulation invoked with the current tick, and fianlly all events are written back to the queue?
On Fri, Jun 11, 2021 at 1:08 PM Majid Jalili <[email protected]> wrote: > Hi, > I am trying to take simpoints for a X86 multicore machine. I compiled > version 21.0.1 for X86_MOESI_Hammer protocol, and applied KVM patches. > Now, I can boot up and see all the cores online. However, when I pass > --take-simpoint-checkpoint arguments with simpoint files and intervals, > what happens is that when the simulator reaches to the simpoints, it stucks > and does not generate the sim points. However, if I do not launch > ruby (--ruby) simulator starts writing the checkpoints and exits. I know > ruby has to flush the caches, and thus it may take time. However, I waited > for more than 2 hours and it never got to the "writing checkpoint" stage. > > Majid >
_______________________________________________ gem5-users mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
