The main execeutable is a command-line application called `inspector'.
If run without arguments, inspector will perform all available
benchmarks and print the results to stdout.  To change this behavior a
number of options are available.  Run inpsector -h to receive the
following information:

Usage: inspector [-b <bm1>[,<bm2>,...]] [-c <config>] [-o output]
                 [-t <trials>] [-r <runtime>] [-v [<verbosity>]] [-i] [-h|?]
Options:
  -b : list of benchmarks numbers or mneumonics
  -c : input configuration file
  -o : output configuration file
  -t : number of times to repeat each test [default=3]
  -r : minimum time to run one trial [default=1000000 (1 sec.)]
  -v : verbosity level
  -i : run in interactive mode
  -h : print this information

The key option, -b, allows the user to list which benchmarks should be
run.  The list can be comprised of mneumonics or benchmark numbers.  A
couple of bundled mneumonics are provided to simplify running certain
sets of related benchmarks.

Bundled Benchmarks:
  all    : run all benchmarks
  caches : run all cache related benchmarks
  tlbs   : run all tlb related benchmarks
Individual Benchmarks:
  0. cacheSize    : Cache Size/Levels
  1. cacheShare   : Cache Share
  2. cacheLine    : Cache Line Size
  3. cacheAssoc   : Cache Associativity
  4. cacheReplace : Cache Replacement Policy
  5. cacheWrite   : Cache Write Policy
  6. cacheAddress : Cache Indexing (Virtual/Physical)
  7. tlbPage      : TLB Page Size
  8. tlbEntries   : TLB Entry Count
  9. tlbAssoc     : TLB Associativity

Mob works with configuration files which describe the components of
the memory system.  Each component has its own section with a list of
key/value pairs for each property detected.  These configuration files
are human editable and can be used as input (-c option) to supply
initial values to the benchmarks.  Some benchmarks are dependant upon
the result of others.  If sufficient information is not provided
through an input configuration file then the appropriate benchmark
will be run automatically to determine the necessary values.  If the
-o option is not supplied to direct the output configuration to a
file, the results are printed directly to stdout.

In addition to the output configuration file, mob can also print
different levels of intermediate data to allow the user to analyze the
benchmark results himself.  A number of verbosity levels control how
much additional information is displayed.  The special `plot'
verbosity level produces a special output format that can be fed
through a supplied script, `mob-plot', to generate graphs through
gnuplot.

Verbosity Levels
  0 : quiet - nothing is printed
  1 : plot - special output for graphing
  2 : normal - normal printing of results
  3 : warn - include configuration warnings
  4 : inspect - display intermediate test values
  5 : debug - print low-level test parameters
  6 : all - print everything