No description
40174f119d
dev/ns_gige.cc:
Clean up the interrupt code. Do a better job determining when
coalescing should happen.
Remove some bogus comments
Stop using magic numbers in initialization and comment what
the various numbers do
dev/ns_gige_reg.h:
#define describing which interrupts cannot be delayed and
which interrrupts we don't implement
--HG--
extra : convert_revision : eb196afa0bf448e1849dd2bd30dde32134effee7
|
||
|---|---|---|
| arch | ||
| base | ||
| build | ||
| configs/boot | ||
| cpu | ||
| dev | ||
| docs | ||
| kern | ||
| sim | ||
| test | ||
| util | ||
| Doxyfile | ||
| LICENSE | ||
| README | ||
| SConscript | ||
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 ply and libelf) M5 is a capable, full-system simulator that current supports both Linux 2.4/2.6 and the proprietary Compaq/HP Tru64 version of Unix. We are able to distribute Linux bootdisks, but we are unable to distribute bootable disk images of Tru64 Unix. If you have a Tru64 license and are interested in obtaining disk images, contact us at m5-dev@eecs.umich.edu. WHAT'S NEEDED ------------- -GCC(3.X) -Python(2.2.2+) WHAT'S RECOMMENDED ------------------ -MySQL (for statistics complex statistics storage/retrieval) -Python-MysqlDB (for statistics analysis) 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. There are three different build targets and three optimizations in each level: Target: ------- ALPHA - Syscall emulation simulation KERNEL - Linux full system simulation KERNEL_TLASER - Tru64 Unix full system simulation Optimization: ------------- m5.debug - debug version of the code with tracing and without optimization m5.opt - optimized version of code with tracing m5.fast - optimized version of the code without tracing and asserts cd $top/m5/build scons TARGET/OPTLEVL # e.g. KERNEL/m5.opt, use -j N if you have a MP system cd $top/m5-test ./do-tests.pl -B ALPHA # test what you just built ./do-tests.pl -B KERNEL # test what you just built # wait for tests to run... # should end with "finished do-tests successfully!"