diff options
author | Nilay Vaish <nilay@cs.wisc.edu> | 2012-01-11 13:50:18 -0600 |
---|---|---|
committer | Nilay Vaish <nilay@cs.wisc.edu> | 2012-01-11 13:50:18 -0600 |
commit | 03229f25759898ea2f82ef3e4fe761c452a49701 (patch) | |
tree | c6225315ca2964bced98b476a60cb1d16fd61cc9 /src/mem/ruby/system/MemoryNode.cc | |
parent | bf59a9298f6154cb85ebebabd4f45738caf29b35 (diff) | |
download | gem5-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 'src/mem/ruby/system/MemoryNode.cc')
0 files changed, 0 insertions, 0 deletions