Brad, I also see the protocol getting into a dead lock. I tried to get a
trace, but I get segmentation fault (yes, the segmentation fault only
occurs when trace flag ProtocolTrace is supplied). It seems to me that
memory is getting corrupted somewhere, because the fault occurs in malloc
it self.
It could be that protocol is actually not in a dead lock. Both Arka and I
had increased the deadlock threashold while testing the protocol. I will
try with increased threashold later in the day.
One more thing, the Orion 2.0 code that was committed last night makes use
of printf(). It did not compile cleanly for me. I had change it fatal()
and include the header file base/misc.hh.
--
Nilay
On Mon, 7 Feb 2011, Beckmann, Brad wrote:
FYI...If my local regression tests are correct. This patch does not fix
all the problems with the MESI_CMP_directory protocol. One of the
patches I just checked in fixes a subtle bug in the ruby_mem_test.
Fixing this bug, exposes more deadlock problems in the
MESI_CMP_directory protocol.
To reproduce the regression tester's sequencer deadlock error, set the
Randomization flag to false in the file configs/example/ruby_mem_test.py
then run the following command:
build/ALPHA_SE_MESI_CMP_directory/m5.debug configs/example/ruby_mem_test.py -n 8
Let me know if you have any questions,
Brad
-----Original Message-----
From: m5-dev-boun...@m5sim.org [mailto:m5-dev-boun...@m5sim.org]
On Behalf Of Nilay Vaish
Sent: Thursday, January 13, 2011 8:50 PM
To: m5-dev@m5sim.org
Subject: [m5-dev] changeset in m5: Ruby: Fixes MESI CMP directory protocol
changeset 8f37a23e02d7 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=8f37a23e02d7
description:
Ruby: Fixes MESI CMP directory protocol
The current implementation of MESI CMP directory protocol is
broken.
This patch, from Arkaprava Basu, fixes the protocol.
diffstat:
_______________________________________________
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
