No description
667cbb6690
resetstats
dumpstats
dumpresetstats
m5checkpoint
Lots of cleanup of serialization and stats dumping/resetting to
work with these new instructions
arch/alpha/isa_desc:
Implement more m5 pseduo opcodes:
resetstats
dumpstats
dumpresetstats
m5checkpoint
All of these functions take two optional parameters, the first is a delay,
and the second is a period. The delay tells the simulator to wait the
specified number of nanoseconds before triggering the event, the period
tells the simulator to repeat the event with a specified frequency
base/statistics.cc:
base/statistics.hh:
regReset RegResetCallback
dev/disk_image.cc:
serializeFilename -> CheckpointFile()
sim/debug.cc:
Move this debugging statement to sim_stats.cc
sim/eventq.cc:
Don't AutoDelete an event if it is scheduled since the process()
function could potentially schedule the event again.
sim/main.cc:
DumpStatsEvent is now Statistics::SetupEvent(Dump, curTick)
sim/serialize.cc:
Change the serialize event so that it's possible to cause the
event to repeat. Also make the priority such that the event
happens just before the simulator would exit if both events
were scheduled for the same cycle.
get rid of the serializeFilename variable and provide a CheckpointFile()
function. This function takes a basename that is set in the
configuration, and appends the current cycle to the name so that
multiple checkpoints can be dumped from the same simulation.
Also, don't exit the simulation when a checkpoint file is dumped.
sim/serialize.hh:
serializeFilename -> CheckpointFile()
SetupCheckpoint function to tell the simulator to prepare
to checkpoint at a certain time with a certain period
sim/sim_events.cc:
DumpStatsEvent stuff gets move to sim_stats.(cc|hh)
The context stuff gets moved into the already existing
stats context in stat_context.cc
sim/sim_events.hh:
DumpStatsEvent stuff gets move to sim_stats.(cc|hh)
sim/universe.cc:
Provide some simple functions for converting times into
ticks. These use floating point math to get as close as
possible to the real values. Multipliers are set up ahead
of time
--HG--
extra : convert_revision : d06ef26a9237529a1e5060cb1ac2dcc04d4ec252
|
||
|---|---|---|
| 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.