Difference between revisions of "M5ops"
From gem5
					
										
					
					 (→The m5 Utility (FS mode))  | 
				 (→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:  | + | * ivlb: Deprecated, present only for old binary compatibility  | 
| − | * ivle:  | + | * ivle: Deprecated, present only for old binary compatibility  | 
| − | * initparam:  | + | * initparam: Deprecated, present only for old binary compatibility  | 
| − | * sw99param:  | + | * sw99param: Deprecated, present only for old binary compatibility  | 
* exit [''delay'']: Stop the simulation in ''delay'' ticks.  | * exit [''delay'']: Stop the simulation in ''delay'' ticks.  | ||
* resetstats [''delay'' [''period'']]: Reset simulation statistics in ''delay'' ticks; repeat this every ''period'' ticks.  | * resetstats [''delay'' [''period'']]: Reset simulation statistics in ''delay'' ticks; repeat this every ''period'' ticks.  | ||
| Line 14: | Line 14: | ||
* dumpresetstats [''delay'' [''period'']]: same as ''resetstats; dumpstats''  | * dumpresetstats [''delay'' [''period'']]: same as ''resetstats; dumpstats''  | ||
* 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: Print the file specified by the config parameter system.readfile. This is how the the rcS files are copied into the simulation environment.  | 
| − | * debugbreak:  | + | * debugbreak: Call debug_break() in the simulator (causes simulator to get SIGTRAP signal, useful if debugging with GDB).  | 
| − | * switchcpu:  | + | * switchcpu: Cause an exit event of type, "switch cpu," allowing the Python to switch to a different CPU model if desired.  | 
Revision as of 13:32, 19 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: Deprecated, present only for old binary compatibility
 - ivle: Deprecated, present only for old binary compatibility
 - initparam: Deprecated, present only for old binary compatibility
 - sw99param: Deprecated, present only for old binary compatibility
 - 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: Print the file specified by the config parameter system.readfile. This is how the the rcS files are copied into the simulation environment.
 - debugbreak: Call debug_break() in the simulator (causes simulator to get SIGTRAP signal, useful if debugging with GDB).
 - switchcpu: Cause an exit event of type, "switch cpu," allowing the Python to switch to a different CPU model if desired.