On Tue, 12 May 2015, Brad Beckmann wrote:
On May 12, 2015, 3:52 p.m., Nilay Vaish wrote:
configs/ruby/MESI_Three_Level.py, line 106
<http://reviews.gem5.org/r/2776/diff/1/?file=45127#file45127line106>
Can you explain the rationale behind this change?
As I mentioned in response to Jason's review, this code is broken when
running the tester with multiple CPUs. I believe this is the same issue
you mentioned a couple weeks ago correct?
I am going to ask the same question again. Why setting the clock of a
controller to the cpu that talks to it incorrect?
--
Nilay
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
