Difference between revisions of "M5ops"
From gem5
(created page, please review.) |
(→The m5 Utility (FS mode)) |
||
| Line 5: | Line 5: | ||
The m5 utility (see util/m5/) can be used in FS mode to issue special instructions to trigger simulation specific functionality. It currently offers the following options: | The m5 utility (see util/m5/) can be used in FS mode to issue special instructions to trigger simulation specific functionality. It currently offers the following options: | ||
| + | * ivlb: | ||
| + | * ivle: | ||
* initparam: | * initparam: | ||
* sw99param: | * sw99param: | ||
| Line 13: | Line 15: | ||
* checkpoint [''delay'' [''period'']]: Create a checkpoint in ''delay'' ticks; repeat this every ''period'' ticks. | * checkpoint [''delay'' [''period'']]: Create a checkpoint in ''delay'' ticks; repeat this every ''period'' ticks. | ||
* readfile: | * readfile: | ||
| + | * debugbreak: | ||
| + | * switchcpu: | ||
Revision as of 07:03, 3 September 2007
This page explains the special opcodes that can be used in M5 to do checkpoints etc.
The m5 Utility (FS mode)
The m5 utility (see util/m5/) can be used in FS mode to issue special instructions to trigger simulation specific functionality. It currently offers the following options:
- ivlb:
- ivle:
- initparam:
- sw99param:
- exit [delay]: Stop the simulation in delay ticks.
- resetstats [delay [period]]: Reset simulation statistics in delay ticks; repeat this every period ticks.
- dumpstats [delay [period]]: Save simulation statistics to a file in delay ticks; repeat this every period ticks.
- dumpresetstats [delay [period]]: same as resetstats; dumpstats
- checkpoint [delay [period]]: Create a checkpoint in delay ticks; repeat this every period ticks.
- readfile:
- debugbreak:
- switchcpu:
