On Thu, 6 Jun 2013, Andreas Hansson wrote:
On June 1, 2013, 9:33 a.m., Nilay Vaish wrote:
I think there is no need for this ruby clock. Just set it to cpu clock.
Andreas Hansson wrote:
Really? I am not sure what the Ruby clock corresponds to in a real system,
but if it is interconnect + L2 caches (and beyond) then surely it should not be
the CPU clock?
Ruby includes the entire memory system.
Perhaps I'm missing something about how Ruby treats the clock.
Do we need a more in-depth discussion of what clock domains there should be in a Ruby
"system" and what their counterpart is in a real system?
You can leave that Ruby clock in there if you like. Just move it to the
file configs/ruby/Ruby.py.
--
Nilay
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
