Age | Commit message (Collapse) | Author | |
---|---|---|---|
2016-09-16 | tests, arm: Make switcheroo and checkpoint tests functional | Andreas Sandberg | |
Switcheroo and checkpoint tests should generally be considered to be successful if they run to completion. Remove all reference output files from the switcheroo and checkopint tests to make them purely functional. Change-Id: I70b47853bd662b7a33716d9e0d2154b16077f9dc Signed-off-by: Andreas Sandberg <andreas.sandberg@arm.com> Reviewed-by: Curtis Dunham <curtis.dunham@arm.com> | |||
2016-08-02 | stats: update references | Curtis Dunham | |
2016-07-21 | stats: update references | Curtis Dunham | |
2016-06-02 | stats: Update to match ARM ISA changes | Andreas Sandberg | |
2016-04-08 | stats: update stats for thermals, indirect BP | Curtis Dunham | |
2016-01-22 | stats: update stats to after GPU checkin | Tony Gutierrez | |
2015-12-12 | stats: bump stats to reflect ruby tester changes | Anthony Gutierrez | |
2015-12-05 | stats: Update to reflect changes to PCI handling | Andreas Sandberg | |
2015-12-04 | stats: Update to reflect changes to RealView platform code | Andreas Sandberg | |
2015-11-16 | stats: updates due to recent chagnesets | Nilay Vaish | |
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-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. |