Hi all, Currently, I'm trying to simulate some parsec benchmarks on a Ruby + Garnet system, using Mesh; 8 cpus, L1 and L2; X86_MESI_Two_Level protocol, for example.
Unfortunatelly, the simulations have been stopped by an deadlock detection, after some minutes starting the workload (e.g. blackscholes). The deadlock_threshold is set up to be 500.000 cycles (default value). Questions: - What could happen if I remove this detection? - What do you suggest me to verify what is causing this long access time on the Sequencer? Thank you! -- Atenciosamente, Matheus Alcântara Souza
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
