> On Feb. 1, 2013, 2:17 a.m., Andreas Hansson wrote: > > How come this is in Ticks, and the other patches replace Time with Cycles?
Because the CacheMemory class is not a clocked object, but makes calls to these functions in the replacement policy classes. - Nilay ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/1679/#review3960 ----------------------------------------------------------- On Jan. 29, 2013, 8:29 p.m., Nilay Vaish wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/1679/ > ----------------------------------------------------------- > > (Updated Jan. 29, 2013, 8:29 p.m.) > > > Review request for Default. > > > Description > ------- > > Changeset 9496:95a46459dfa6 > --------------------------- > ruby: replace Time with Tick in replacement policy classes > > > Diffs > ----- > > src/mem/ruby/system/AbstractReplacementPolicy.hh 5dca39cc7641 > src/mem/ruby/system/LRUPolicy.hh 5dca39cc7641 > src/mem/ruby/system/PseudoLRUPolicy.hh 5dca39cc7641 > > Diff: http://reviews.gem5.org/r/1679/diff/ > > > Testing > ------- > > > Thanks, > > Nilay Vaish > > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
