Age | Commit message (Collapse) | Author | |
---|---|---|---|
2015-11-06 | stats: Update stats to match cache changes | Andreas Hansson | |
2015-10-10 | stats: Update for UDelayEvent quiesce change | Joel Hestness | |
2015-09-25 | stats: Update stats to reflect snoop-filter changes | Andreas Hansson | |
2015-09-15 | stats: updates due to recent changesets including d0934b57735a | Nilay Vaish | |
2015-08-07 | stats: Update ARM stats to include programmable oscillators | Andreas Sandberg | |
2015-07-04 | stats: update stale config.ini files, eio and few other stats. | Nilay Vaish | |
2015-07-03 | stats: Update stats for cache, crossbar and DRAM changes | Andreas Hansson | |
This update includes the changes to whole-line writes, the refinement of Read to ReadClean and ReadShared, the introduction of CleanEvict for snoop-filter tracking, and updates to the DRAM command scheduler for bank-group-aware scheduling. Needless to say, almost every regression is affected. | |||
2015-05-05 | stats: Update stats to reflect cache changes | Andreas Hansson | |
2015-04-03 | stats: updates due to recent changesets. | Nilay Vaish | |
2015-03-19 | test, arm: Add scripts to test checkpoints | Andreas Sandberg | |
Add a set of scripts to automatically test checkpointing in the regression framework. The checkpointing tests are similar to the switcheroo tests, but instead of switching between CPUs, they checkpoint the system and restore from the checkpoint again. This is done at regular intervals, typically while booting Linux. The implementation is fairly straight forward, with the exception that we have to work around gem5's inability to restore from a checkpoint after a system has been instantiated. We work around this by forking off child processes that does the actual simulation and never instantiate a system in the parent process unless a maximum checkpoint count is reached (in which case we just simulate the system to completion in the parent). Checkpoint testing is currently only enabled 32- and 64-bit ARM systems using atomic CPUs. Note: An unfortunate side-effect of forking is that every new process will overwrite the stats and terminal output from the previous process. This means that the output directory only contains data from the last checkpoint. |