Now that the multiple eventq patch is in the repo, it is time to discuss
the steps that we should be taking next. In past, I have tried making
caches in ruby use the same eventq as the owner cpu. Since a lot
information in being recorded in a centralized fashion, it is difficult to
get this right. While some of this has changed since I modified the way
statistics are collected in ruby, this always gets me into thinking about
how this might affect the performance of a single threaded simulation.
What do other developers think we should be doing next?
--
Nilay
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev