changeset 685719afafe6 in /z/repo/m5 details: http://repo.m5sim.org/m5?cmd=changeset;node=685719afafe6 description: memtest: due to contention increase, increased deadlock threshold
diffstat: configs/example/ruby_mem_test.py | 6 ++++++ tests/configs/memtest-ruby.py | 6 ++++++ 2 files changed, 12 insertions(+), 0 deletions(-) diffs (32 lines): diff -r bb6411d45356 -r 685719afafe6 configs/example/ruby_mem_test.py --- a/configs/example/ruby_mem_test.py Tue Feb 08 15:52:44 2011 -0800 +++ b/configs/example/ruby_mem_test.py Tue Feb 08 15:53:33 2011 -0800 @@ -135,6 +135,12 @@ cpu.test = system.ruby.cpu_ruby_ports[i].port cpu.functional = system.funcmem.port + # + # Since the memtester is incredibly bursty, increase the deadlock + # threshold to 5 million cycles + # + system.ruby.cpu_ruby_ports[i].deadlock_threshold = 5000000 + for (i, dma) in enumerate(dmas): # # Tie the dma memtester ports to the correct functional port diff -r bb6411d45356 -r 685719afafe6 tests/configs/memtest-ruby.py --- a/tests/configs/memtest-ruby.py Tue Feb 08 15:52:44 2011 -0800 +++ b/tests/configs/memtest-ruby.py Tue Feb 08 15:53:33 2011 -0800 @@ -96,6 +96,12 @@ # cpus[i].test = ruby_port.port cpus[i].functional = system.funcmem.port + + # + # Since the memtester is incredibly bursty, increase the deadlock + # threshold to 1 million cycles + # + ruby_port.deadlock_threshold = 1000000 # ----------------------- # run simulation _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev