25a358983a
Add support for generic visitors for stats and use them
to implement independent output functions.
Support for mysql output and some initial code for hacking
on mysql output with python
arch/alpha/pseudo_inst.cc:
base/hybrid_pred.cc:
base/hybrid_pred.hh:
base/sat_counter.cc:
base/sat_counter.hh:
cpu/simple_cpu/simple_cpu.cc:
kern/tru64/tru64_events.cc:
sim/main.cc:
sim/process.cc:
sim/process.hh:
sim/sim_events.cc:
sim/sim_object.cc:
sim/system.hh:
update for changes in stats package
base/statistics.cc:
move the python output code to base/stats/puthon.(cc|hh)
and reimplement it as a visitor.
move the text output code to base/stats/text.(cc|hh) and
reimplement it as a visitor.
move the database stuff into base/stats/statdb.(cc|hh) and
get rid of the class. Put everything as globals in the
Statistics::Database namespace.
allocate unique ids for all stats.
directly implement the check routine and get rid of the
various dumping routines since they're now in separate files.
make sure that no two stats have the same name
clean up some loops
base/statistics.hh:
major changes to the statistics package again
lots of code was factored out of statistics.hh into several
separate files in base/stats/ (this will continue)
There are now two Stat package types Result and Counter that
are specified to allow the user to keep the counted type
separate from the result type. They are currently both doubles
but that's an experiment. There is no more per stat ability to
set the type. Statistics::Counter is not the same as Counter!
Implement a visitor for statistics output so that new output
types can be implemented independently from the stats package
itself.
Add a unique id to each stat so that it can be used to keep
track of stats more simply. This number can also be used in
debugging problems with stats.
Tweak the bucket size stuff a bit to make it work better.
fixed VectorDist size bug
cpu/memtest/memtest.cc:
Fix up for changes in stats package
Don't use value() since it doesn't work with binning. If you
want a number as a stat, and to use it in the program itself,
you really want two separate variables, one that's a stat,
and one that's not.
cpu/memtest/memtest.hh:
Fix up for changes in stats package
test/Makefile:
Try to build stuff now that directories matter
test/stattest.cc:
test all new output types
choose which one with command line options
--HG--
extra : convert_revision : e3a3f5f0828c67c0e2de415d936ad240adaddc89
|
||
|---|---|---|
| arch | ||
| base | ||
| cpu | ||
| dev | ||
| docs | ||
| kern/tru64 | ||
| sim | ||
| test | ||
| util | ||
| Doxyfile | ||
| LICENSE | ||
| README | ||
This is release m5_1.0_beta1 of the M5 simulator. This file contains brief "getting started" information and release notes. For more information, see http://m5.eecs.umich.edu. If you have questions, please send mail to m5sim-users@lists.sourceforge.net. WHAT'S INCLUDED (AND NOT) ------------------------- Since you're reading this file, presumably you've managed to untar the distribution. The archive you've unpacked has three subdirectories: - m5: the simulator itself - m5-test: regression tests and scripts to run them - ext: less-common external packages needed to build m5 (currently just "ply") Although M5 is capable of full-system simulation, the only OS it currently supports is the proprietary Compaq/HP Tru64 version of Unix. We are thus unable to distribute bootable disk images freely. If you have a Tru64 license and are interested in obtaining disk images, contact us at m5-dev@eecs.umich.edu. GETTING STARTED --------------- The following steps will build and test the simulator. The variable "$top" refers to the top directory where you've unpacked the files, i.e., the one containing the m5, m5-test, and ext directories. cd $top/m5/setup ./setup ALPHA # set up build/ALPHA directory cd $top/m5/build/ALPHA make m5.opt # use "-j N" if you've got an MP system # wait for build... cd $top/m5-test ./do-tests.pl -B ALPHA # test what you just built # wait for tests to run... # should end with "finished do-tests successfully!" If you run into errors regarding m5/arch/alpha/decoder.cc, just "touch" that file to update its timestamp. This file is generated from a compact ISA description using a program written in Python. If you have Python 2.2.2 or later installed on your system, you should be able to generate it yourself, but if you don't have Python (or have an older version), you may run in to trouble. Since we've shipped a working copy of decoder.cc, it's not necessary to have Python to build M5 (unless you start modifying the ISA decription). Unfortunately, sometimes make gets confused and tries to do so anyway. The "touch" should convince make to stop trying.