Using SPAT: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
== Using SPAT == | |||
See page 16 on setting up environment variables. | |||
setenv CNY_SPAT_CMD “trace_func_all" | |||
setenv CNY_SPAT_MAX 30000 | |||
Run the simulator using the ./run script. The simulator should collect trace data to a spat.dat file. | |||
Run spat. | |||
== Using the -WAMA Flag == | == Using the -WAMA Flag == | ||
Pages 28-30: | Pages 28-30: | ||
Revision as of 16:10, 27 February 2012
Using SPAT
See page 16 on setting up environment variables.
setenv CNY_SPAT_CMD “trace_func_all" setenv CNY_SPAT_MAX 30000
Run the simulator using the ./run script. The simulator should collect trace data to a spat.dat file.
Run spat.
Using the -WAMA Flag
Pages 28-30:
Tells you the % time each memory controller is busy and the % of bandwidth each MC uses (max 12.5%):
