FYI. ClockedObject is it's own type, so if you don't need the other stuff in MemObject (ports), you can just use ClockedObject directly.
On Tue, Aug 21, 2012 at 7:41 PM, Joel Hestness <[email protected]> wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/1362/ > ----------------------------------------------------------- > > (Updated Aug. 21, 2012, 7:41 p.m.) > > > Review request for Default. > > > Changes > ------- > > Per Nilay's recommendation, shifted MemoryController over to MemObject to get > ClockedObject semantics. > > > Description > ------- > > Changeset 9156:0cdcf94f243f > --------------------------- > Ruby Memory Controller: Fix clocking > > Changeset 8937 switched the Ruby memory controller over to using the gem5 > event queue instead of the Ruby event queue, but it did not correctly > implement the clocking of the memory controller. This patch fixes that > functionality by changing the memory controller over to traditional gem5 > frequency specification. > > > Diffs (updated) > ----- > > src/mem/ruby/system/MemoryControl.hh 019047ead23b > src/mem/ruby/system/MemoryControl.cc 019047ead23b > src/mem/ruby/system/MemoryControl.py 019047ead23b > src/mem/ruby/system/RubyMemoryControl.hh 019047ead23b > src/mem/ruby/system/RubyMemoryControl.cc 019047ead23b > src/mem/ruby/system/RubyMemoryControl.py 019047ead23b > > Diff: http://reviews.gem5.org/r/1362/diff/ > > > Testing > ------- > > > Thanks, > > Joel Hestness > > _______________________________________________ > gem5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/gem5-dev _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
