Go to file
Lisa Hsu 921b1ee87b Add the ability to track stats in user defined sets of function calls. code can be generated via the base/instrum_codegen.pl script to easily change the functions being tracked. the only thing the user needs to do is add code in tru64System to change how the callerMap is populated.
command line:

m5.* <config file> <args> --server.system:bin=true to track function calls in the server
m5.* <config file> <args> --client.system:bin=true to track function calls in the client

base/statistics.cc:
    make an adjustment to the way stats are printed for FS_MEASURE
base/statistics.hh:
    add a name() virtual function to GenBin.  add a debug printf for activate().
    add amake MainBin the default bin when FS_MEASURE.
cpu/exec_context.cc:
    initialize swCtx to null upon creation of an xc
cpu/exec_context.hh:
    add a SWContext pointer to every execution context.
cpu/simple_cpu/simple_cpu.cc:
    process calls and returns for FS_MEASURE
cpu/simple_cpu/simple_cpu.hh:
    add this so idleCycles will not be accessed before all stats are constructed
kern/tru64/tru64_events.cc:
    add a FnEvent that fires whenever a function we're tracking is called.  implement the process() virtual function for it.
kern/tru64/tru64_events.hh:
    add FnEvent
kern/tru64/tru64_system.cc:
    send bin parameter to System constructor.  add bin parameter to Tru64System object.  initialize all the FnEvent and MainBin members of Tru64system.  also, populate the calling map that indicates whether a function call is on the path we're tracking.
kern/tru64/tru64_system.hh:
    modify the Tru64System class to support FS_MEASURE
sim/system.cc:
    add a bin parameter to System class.  initialize a MainBin to hold the stats for nonPath.
sim/system.hh:
    add a map of to match bins to function names.  add a swCtx map to map pcb addresses to SWContext *s.  Add some supporting functions.

--HG--
extra : convert_revision : af3eadd798cb2d2aed9b54e1059dcedf244dd526
2003-11-04 15:15:12 -05:00
arch Make it so the quiesce instruction is conditionally enabled 2003-11-03 16:47:08 -05:00
base Add the ability to track stats in user defined sets of function calls. code can be generated via the base/instrum_codegen.pl script to easily change the functions being tracked. the only thing the user needs to do is add code in tru64System to change how the callerMap is populated. 2003-11-04 15:15:12 -05:00
cpu Add the ability to track stats in user defined sets of function calls. code can be generated via the base/instrum_codegen.pl script to easily change the functions being tracked. the only thing the user needs to do is add code in tru64System to change how the callerMap is populated. 2003-11-04 15:15:12 -05:00
dev Implement more m5 pseduo opcodes: 2003-11-02 18:02:58 -05:00
docs footer.html: 2003-10-15 20:49:12 -04:00
kern/tru64 Add the ability to track stats in user defined sets of function calls. code can be generated via the base/instrum_codegen.pl script to easily change the functions being tracked. the only thing the user needs to do is add code in tru64System to change how the callerMap is populated. 2003-11-04 15:15:12 -05:00
sim Add the ability to track stats in user defined sets of function calls. code can be generated via the base/instrum_codegen.pl script to easily change the functions being tracked. the only thing the user needs to do is add code in tru64System to change how the callerMap is populated. 2003-11-04 15:15:12 -05:00
test Make the to_number function work better. 2003-10-31 18:27:17 -05:00
util If a filter isn't specified, don't try to do any filtering 2003-11-02 02:13:04 -05:00
Doxyfile Add FALRU stats, tweak doxygen configs a bit. 2003-10-17 17:51:08 -04:00
LICENSE Import changeset 2003-10-07 10:41:54 -04:00
README Add a README for the release. Ideally we would move this up a level (to the 2003-10-17 09:32:00 -07:00

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.