*
build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MESI_CMP_directory
FAILED!
*
build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MESI_CMP_directory
FAILED!
*
I found the error in MESI CMP. In the L2 cache controller, when the TBE is
deallocated, the pointer was not being set to NULL.
--
Nilay
On Mon, 7 Feb 2011, Arkaprava Basu wrote:
Nilay,
If the same test completes with larger threshold then it certainly a
case of false positive and
changeset 9c245e375e05 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=9c245e375e05
description:
MESI CMP: Unset TBE pointer in L2 cache controller
The TBE pointer in the MESI CMP implementation was not being set to NULL
when the TBE is deallocated. This
Hi Brad, did you miss out on the '_' in _dma_devices?
--
Nilay
diff -r 6f5299ff8260 -r 00ad807ed2ca configs/example/ruby_fs.py
--- a/configs/example/ruby_fs.pySun Feb 06 22:14:18 2011 -0800
+++ b/configs/example/ruby_fs.pySun Feb 06 22:14:18 2011 -0800
@@ -109,12 +109,19 @@
Hi Gabe,
Since you successfully updated the tests I can't run (ARM_FS), I can take of
the remaining errors (i.e. ruby protocol tests). I have a few minor fixes I
want to check in that I need to run the regression tester against anyways.
Brad
-Original Message-
From:
Ah, yes I did. This actually reminds me that I need to fix how dma devices are
connected within Ruby for x86_FS. I'll push a batch that fixes these issues
soon.
Brad
-Original Message-
From: m5-dev-boun...@m5sim.org [mailto:m5-dev-boun...@m5sim.org]
On Behalf Of Nilay Vaish
Hi Korey,
Just to clarify, the deadlock threshold in the sequencer is different than the
deadlock threshold in the mem tester. The sequencer's deadlock mechanism
detects whether any particular request takes longer than the threshold.
Meanwhile the mem tester deadlock threshold just ensures
changeset bb6411d45356 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=bb6411d45356
description:
config: fixed minor bug connecting dma devices to ruby
diffstat:
configs/common/FSConfig.py | 3 +++
configs/example/ruby_fs.py | 12 +---
2 files changed, 8
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
