ruby: reset timing after cache warm up
Review Request #1435 - Created Sept. 24, 2012 and submitted
| Information | |
|---|---|
| Nilay Vaish | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
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.
Issue Summary
1
1
0
0
| Description | From | Last Updated | Status |
|---|---|---|---|
| I think this comment could be better and mention this is only for ruby warming up. There is probably as ... | Ali Saidi | Sept. 26, 2012, 11:10 a.m. | Open |
Posted (Sept. 26, 2012, 8:24 a.m.)
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...
Posted (Sept. 26, 2012, 11:10 a.m.)
-
src/sim/clocked_object.hh (Diff revision 1) -
I think this comment could be better and mention this is only for ruby warming up. There is probably as is missing as well.
Ship It!
Review request changed
Updated (Oct. 4, 2012, 1:29 a.m.)
Description: |
|
||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Diff: |
Revision 2 (+16 -2) |
