> > Is there no other way Ruby could restore the cache state without advancing > time?
No. Setting ruby state requires you to step through the necessary transient states and there is no clear way to know when all those transient states have been completely stepped through without waiting for the eventqueue to be empty. Brad > > > - Andreas > > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/1435/#review3525 > ----------------------------------------------------------- > > > On Sept. 24, 2012, 5:53 p.m., Nilay Vaish wrote: > > > > ----------------------------------------------------------- > > This is an automatically generated e-mail. To reply, visit: > > http://reviews.gem5.org/r/1435/ > > ----------------------------------------------------------- > > > > (Updated Sept. 24, 2012, 5:53 p.m.) > > > > > > Review request for Default. > > > > > > Description > > ------- > > > > Changeset 9249:4b5ef2c0dbd4 > > --------------------------- > > ruby: reset timing after cache warm up Ruby system was recently > > converted to a clocked object. Such objects maintain state related to > > the time that has passed so far. During the cache warmup, Ruby system > > changes its own time and the global time. Later on, the global time is > > restored. So Ruby system also needs to reset its own time. > > > > > > Diffs > > ----- > > > > src/mem/ruby/system/System.cc 73c3eb0dd733 > > src/sim/clocked_object.hh 73c3eb0dd733 > > > > Diff: http://reviews.gem5.org/r/1435/diff/ > > > > > > Testing > > ------- > > > > > > Thanks, > > > > Nilay Vaish > > > > > > _______________________________________________ > 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
