summaryrefslogtreecommitdiff
path: root/configs/common/Options.py
diff options
context:
space:
mode:
authorNilay Vaish <nilay@cs.wisc.edu>2012-01-11 13:50:18 -0600
committerNilay Vaish <nilay@cs.wisc.edu>2012-01-11 13:50:18 -0600
commit03229f25759898ea2f82ef3e4fe761c452a49701 (patch)
treec6225315ca2964bced98b476a60cb1d16fd61cc9 /configs/common/Options.py
parentbf59a9298f6154cb85ebebabd4f45738caf29b35 (diff)
downloadgem5-03229f25759898ea2f82ef3e4fe761c452a49701.tar.xz
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.
Diffstat (limited to 'configs/common/Options.py')
-rw-r--r--configs/common/Options.py4
1 files changed, 4 insertions, 0 deletions
diff --git a/configs/common/Options.py b/configs/common/Options.py
index ff4acbe37..1941875bc 100644
--- a/configs/common/Options.py
+++ b/configs/common/Options.py
@@ -85,6 +85,10 @@ parser.add_option("--work-end-checkpoint-count", action="store", type="int",
help="checkpoint at specified work end count")
parser.add_option("--work-cpus-checkpoint-count", action="store", type="int",
help="checkpoint and exit when active cpu count is reached")
+parser.add_option("--restore-with-cpu", action="store", type="choice",
+ default="atomic", choices = ["atomic", "timing",
+ "detailed", "inorder"],
+ help = "cpu type for restoring from a checkpoint")
# CPU Switching - default switch model goes from a checkpoint