> > We could even create a ClockedObject that has a clock and some > > functions for scheduling based on cycles. This would make it even > > easier. > > > Along these lines, if we are going to create this ClockedObject, then > we > should also start having Ruby's objects (caches/switches/etc.) > interpret > absolute latencies off the command line (e.g. '1ns') instead of cycles > as > it gets really confusing when you have systems where the network runs > at > different speeds then the CPUs (or other "classic" M5 objects). >
We can do certainly do that. Once we get this cache warmup fix complete, I see that sort of change as a nice follow-on fix. Brad _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
