sanchayanmaity/gem5
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

memtest: due to contention increase, increased deadlock threshold

Browse source
This commit is contained in:
Brad Beckmann 2011-02-08 15:53:33 -08:00
parent 6ebd7c390b
commit ea9d4c3a97
2 changed files with 12 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
configs/example/ruby_mem_test.py
View file

@ -135,6 +135,12 @@ for (i, cpu) in enumerate(cpus):
cpu.test = system.ruby.cpu_ruby_ports[i].port cpu.test = system.ruby.cpu_ruby_ports[i].port
cpu.functional = system.funcmem.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): for (i, dma) in enumerate(dmas):
# #
# Tie the dma memtester ports to the correct functional port # Tie the dma memtester ports to the correct functional port

6
tests/configs/memtest-ruby.py
View file

@ -97,6 +97,12 @@ for (i, ruby_port) in enumerate(system.ruby.cpu_ruby_ports):
cpus[i].test = ruby_port.port cpus[i].test = ruby_port.port
cpus[i].functional = system.funcmem.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 # run simulation
# ----------------------- # -----------------------