On Mon, 13 Oct 2014, Andreas Hansson via gem5-dev wrote:
Hi all,
With Nilay’s recent improvements to Ruby I would like to understand if
there is any point in still having the RubyMemoryControl, or if we
should just clean things up a bit and remove it. I would think the best
way forward is to clean up the integration of Ruby and classic and
ensure that there is no duplicated functionality beyond what is strictly
necessary.
Nilay, do you think this would make sense? Is there anyone else with any
opinions in this matter?
I was in favor of dropping RubyMemoryControl. But I had some discussion
with Brad Beckmann from AMD. Since AMD has some infrastructure in place
already, they would like to retain RubyMemoryControl for the time being.
I suggest that we retain the memory controller code in ruby for another
six months or so, and then we will drop it. In the mean time, we
will update the interface so that ruby protocols can use classic memory
controller. The code for this is already on the reviewboard. Over this
six month period, I hope, most users would have switched to using classic
controller.
Thanks
Nilay
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
