On Fri, February 1, 2013 8:22 am, Andreas Hansson wrote: > > >> 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? >> >> Nilay Vaish wrote: >> Because the CacheMemory class is not a clocked object, but makes >> calls to >> these functions in the replacement policy classes. > > Would it be an option to make it a ClockedObject (or is that overkill)? >
I think it would too much. The controller associated with the cache is aclocked object. Had the controller been in C++, I would have passed cycle value using its clock. But the controller is in SLICC and would require lot more changes. -- Nilay _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
