Sniper configuration - Revision history

Wheirman at 18:51, 27 March 2012

2012-03-27T18:51:52Z

Wheirman at 15:57, 26 March 2012

2012-03-26T15:57:24Z

Wheirman: Created page with "Sniper is configured using command-line parameters and/or configuration files. The default configuration is stored in `sniper/config/default.cfg`. The `run-sniper..."`


2012-01-16T14:21:29Z
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..."
New page
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</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>-g --section/parameter=value</code>: set a single parameter value (e.g. <code>--perf_model/core/frequency=2.66</code>).

← Older revision		Revision as of 18:51, 27 March 2012
Line 3:		Line 3:
	* <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.

Sniper configuration - Revision history

Wheirman at 18:51, 27 March 2012

Wheirman at 15:57, 26 March 2012

Wheirman: Created page with "Sniper is configured using command-line parameters and/or configuration files. The default configuration is stored in sniper/config/default.cfg. The run-sniper..."

Wheirman: Created page with "Sniper is configured using command-line parameters and/or configuration files. The default configuration is stored in `sniper/config/default.cfg`. The `run-sniper..."`