Config: Add support for restoring using a timing CPU
Review Request #977 - Created Jan. 3, 2012 and submitted
| Information | |
|---|---|
| Nilay Vaish | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
Config: Add support for restoring using a timing CPU Currently there is an assumption that restoration from a checkpoint will happen by first restoring to an atomic CPU and then switching to a timing CPU. This patch adds support for directly restoring to a timing CPU. It adds a new option '--restore-with-cpu' which is used to specify the type of CPU to which the checkpoint should be restored to. It defaults to 'atomic' which was the case before.
Posted (Jan. 4, 2012, 12:45 a.m.)
-
configs/common/Options.py (Diff revision 1) -
This should probably be a choices type rather than a string. Might also make sense to have a --cpu option that is also a choices instead of the current atomic/timing/detalied/etc
-
configs/common/Simulation.py (Diff revision 1) -
if you did that then run_with_cpu could go away and you could have options.cpu == options.restore_with_cpu