Running gem5

From gem5
Revision as of 20:22, 31 May 2006 by Saidi (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

M5 uses configuration files to specify simulated system configurations and simulation options. Running M5 is as simple as giving the name of a configuration file (ending in '.py') as a command-line argument.

The configuration file documentation page (Configuration Files Explained) has details on config file format and interpretation. The easiest way to get started is to use an existing configuration file. A variety of config files are provided in the m5/configs directory. Another good source of example config files is the regression test suite in the m5-test directory. Each regression test is executed by specifying the '' file in the test directory as the configuration, e.g., '../m5/build/ALPHA_SE/m5.opt test1/'. Unlike the files in m5/config, the config files in m5-test are tested regularly and are guaranteed to work.

Configuration parameters can also be specified directly on the command line as "--<variable>=<value>" (see Configuration Files Explained). From the simulator's perspective, setting parameters in this fashion is indistinguishable from specifying them in a configuration file. A few parameters typically specified on the command line instead of in a config file are:

--root.trace.flags="SomeFlagString" - turn on event tracing for the specified classes of simulation events --root.trace.start=<start_cycle> - cycle at which the traces indicated by the trace.flags param are to begin dumping --Serialize.cycle=<start_cycle> - dump a checkpoint at this cycle --Serialize.period=<period> - repeat interval for dumping checkpoints --Serialize.count=<number> - number of checkpoints to dump Some configuration parameters require instantiating an actual Python object. To do this on the command line, you can inform m5 that you want a direct python string interpreted using the -P parameter. Here are a few examples:

-P"root.max=Terminate(cycle=1000)" - terminate the simulation at 1000 cycles -P"root.progress=Progress(cycle=100)" - dump a message every 100 cycles (to know that m5 is not hanging) Running m5 with the "-h" flag prints a help message, including basic command-line parameters. Here is what it looks like:

m5.debug [-d <dir>] [-E <var>[=<val>]] [-I <dir>] [-P <python>]
        [--<var>=<val>] <config file>

   -d            set the output directory to <dir>
   -E            set the environment variable <var> to <val> (or 'True')
   -I            add the directory <dir> to python's path
   -P            execute <python> directly in the configuration
   --var=val     set the python variable <var> to '<val>'
   <configfile>  config file name (ends in .py)

m5.debug -X
   -X            extract embedded files

m5.debug -h
   -h            print short help