> On Sept. 26, 2012, 3:24 p.m., Andreas Hansson wrote:
> > I'm not too thrilled about this. Could you explain why we cannot rely on 
> > the global time keeping here? I'm not understanding the issue...
> 
> Andreas Hansson wrote:
>     I'm even inclined to create a ResettableClockedObject in between 
> ClockedObject and the Ruby system. The whole idea of having a function to 
> reset the clock makes me nervous.
>     
>     Is there no other way Ruby could restore the cache state without 
> advancing time?

Andreas, it is not possible to create ResettableClockedObject class. This is
because the variables tick and cycles are private to class ClockedObject and
hence not accessible in ResettableClockedObject.


- Nilay


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/1435/#review3525
-----------------------------------------------------------


On Oct. 4, 2012, 8:29 a.m., Nilay Vaish wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://reviews.gem5.org/r/1435/
> -----------------------------------------------------------
> 
> (Updated Oct. 4, 2012, 8:29 a.m.)
> 
> 
> Review request for Default.
> 
> 
> Description
> -------
> 
> Changeset 9277:f576478175f1
> ---------------------------
> 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 a5ede748a1d9 
>   src/sim/clocked_object.hh a5ede748a1d9 
> 
> 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

Reply via email to