Difference between revisions of "Sniper configuration"
Jump to navigation
Jump to search
(Created page with "Sniper is configured using command-line parameters and/or configuration files. The default configuration is stored in <code>sniper/config/default.cfg</code>. The <code>run-sniper...") |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | Sniper is configured using command-line parameters and/or configuration files. The default configuration is stored in <code>sniper/config/ | + | Sniper is configured using command-line parameters and/or configuration files. The default configuration is stored in <code>sniper/config/base.cfg</code>. The <code>run-sniper</code> script accepts the <code>-c configfile</code> and <code>-g configsetting</code> commandline parameters to modify this. Configuration files or parameters are evaluated from left to right on the commandline, newer values override older ones. |
* <code>-c configfile</code>: includes the configfile configuration file. If no <code>-c</code> option is used, <code>gainestown</code> is automatically assumed which models a Nehalem-like system. <code>configfile</code> can be either an existing filename in the current path (e.g. <code>-c ./myconf.cfg</code>), or it can be the name of a predefined config file in <code>sniper/config</code> without its <code>.cfg</code> extension (e.g. <code>-c gainestown</code> to include <code>sniper/config/gainestown.cfg</code>) | * <code>-c configfile</code>: includes the configfile configuration file. If no <code>-c</code> option is used, <code>gainestown</code> is automatically assumed which models a Nehalem-like system. <code>configfile</code> can be either an existing filename in the current path (e.g. <code>-c ./myconf.cfg</code>), or it can be the name of a predefined config file in <code>sniper/config</code> without its <code>.cfg</code> extension (e.g. <code>-c gainestown</code> to include <code>sniper/config/gainestown.cfg</code>) | ||
* <code>-g --section/parameter=value</code>: set a single parameter value (e.g. <code>--perf_model/core/frequency=2.66</code>). | * <code>-g --section/parameter=value</code>: set a single parameter value (e.g. <code>--perf_model/core/frequency=2.66</code>). | ||
| + | |||
| + | At the start of each simulation, a file <code>sim.cfg</code> is written which contains the complete configuration details used in this run. | ||
Latest revision as of 11:51, 27 March 2012
Sniper is configured using command-line parameters and/or configuration files. The default configuration is stored in sniper/config/base.cfg. The run-sniper script accepts the -c configfile and -g configsetting commandline parameters to modify this. Configuration files or parameters are evaluated from left to right on the commandline, newer values override older ones.
-c configfile: includes the configfile configuration file. If no-coption is used,gainestownis automatically assumed which models a Nehalem-like system.configfilecan be either an existing filename in the current path (e.g.-c ./myconf.cfg), or it can be the name of a predefined config file insniper/configwithout its.cfgextension (e.g.-c gainestownto includesniper/config/gainestown.cfg)-g --section/parameter=value: set a single parameter value (e.g.--perf_model/core/frequency=2.66).
At the start of each simulation, a file sim.cfg is written which contains the complete configuration details used in this run.
