src/mem/ruby/system/MemoryControl.py (Diff revision 1)

How about changing SimObject to ClockedObject? Then, you would not need to 
add a new param clock in RubyMemoryControl.py. You would need to set it though.
You would be able to make use of certain functions that ClockedObject class provides.

1. Joel Hestness Aug. 21, 2012, 9:05 a.m. (Aug. 21, 2012, 9:05 a.m.)

   Will make this change and resubmit.

src/mem/ruby/system/RubyMemoryControl.cc (Diff revision 1)

Joel, this is another line where schedule() is called. You might want to check if it needs to be fixed as well.

1. Joel Hestness Aug. 21, 2012, 9:05 a.m. (Aug. 21, 2012, 9:05 a.m.)

   Yep, I checked this one out.  This schedule call is only used when the memory controller is being woken up from idle by an enqueue call from the directory (i.e. when the cycle event isn't currently scheduled).  Scheduling the wakeup 1 tick after the request arrives seems reasonable.
   
   Separate from this patch, I had also instrumented the code to collect the number of cycles that the memory controller executes for verification purposes.  In a handful of tests, the number of ticks was the appropriate frequency multiple of the number of cycles.

Ship It!