Hi Jinzhu,
The error is that your protocol found an invalid transition when in state "I".
If you grep for "Invalid transition", you will see that this error message was
most likely printed out from build/X86_SE/mem/protocol/L1Cache_Transitions.cc
You can print out a protocol trace in such cases t
Does anyone have some suggestions? I still couldn't figure it
out.thanks!
Jinzhu
On Tue, Jul 31, 2012 at 6:50 PM, gem5 gem5 wrote:
> Hi all,
>
> I want to move the MOSI_SMP_bcast protocol from GEMS to GEM5. I modified
> the original MOSI_SMP_bcast_1level protocol to
> become MOSI_CMP_bcast_
Respected All,
Please i have a problem that blocks me a lot in my thesis ,so any help will
be highly appreciated.
I am running X86 Full system using the link:
https://docs.google.com/document/preview?id=1B7nZSqMLwkwoVNEj_58tMPTk4bKWvoEMbokOAjqeC-k
The command
build/x86/gem5.opt configs/example/f
That is more or less correct. And, if you want to do: fast-forward in
atomic -> warm up in timing -> run in detailed, my patch will almost
certainly work, since bugs have only been observed when switching
back-and-forth repeatedly.
-Tony
On Fri, Aug 3, 2012 at 10:26 AM, Kiyeon Lee wrote:
> Hi,
Hi, Tony and Ali.
Thanks for your quick response. I did not have time to try your patches
yet, but I'm glad to know that there are patches that may help solving my
problem.
Please let me I ask a question to clarify the "draining" problem.
The drain functionality is used to complete all outstanding
