7deb34b24d
The util/pbs directory has a set of python scripts which were written to submit jobs to the PBS pool at the University of Michigan. They aren't incredibly specialized for that environment, but they do have a little bit of hard coding which, for instance, uses paths which are only meaningful there. The util/batch directory was added alongside a seemingly unrelated change (perhaps by accident?) and is a slightly updated copy of util/pbs which also (or instead?) supports OAR. The qdo script seems to be a script for managing job queues on PBS and/or OAR, and is also tuned to the UofM environment, for instance insisting that a path starts with /n/poolfs so that files are available on an NFS volume shared with the pool. All three of these scripts could potentially be useful with modification in a similar environment, but also all three are unmaintained. The environment in UofM may no longer actually match the expectations of these scripts, and even if it does/did, gem5 may no longer be 100% compatible with them. If these scripts sit in util not being used by anyone, they add clutter and complexity without adding any value. If someone really needs to know what was once in them, they can be recovered from revision control. Change-Id: I0192bd119893f7a41fcb820f4cf408609b03cd27 Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/30957 Reviewed-by: Steve Reinhardt <stever@gmail.com> Reviewed-by: Andreas Sandberg <andreas.sandberg@arm.com> Reviewed-by: Jason Lowe-Power <power.jg@gmail.com> Maintainer: Jason Lowe-Power <power.jg@gmail.com> Tested-by: kokoro <noreply+kokoro@google.com>
This is the gem5 simulator. The main website can be found at http://www.gem5.org A good starting point is http://www.gem5.org/about, and for more information about building the simulator and getting started please see http://www.gem5.org/documentation and http://www.gem5.org/documentation/learning_gem5/introduction. To build gem5, you will need the following software: g++ or clang, Python (gem5 links in the Python interpreter), SCons, SWIG, zlib, m4, and lastly protobuf if you want trace capture and playback support. Please see http://www.gem5.org/documentation/general_docs/building for more details concerning the minimum versions of the aforementioned tools. Once you have all dependencies resolved, type 'scons build/<ARCH>/gem5.opt' where ARCH is one of ARM, NULL, MIPS, POWER, SPARC, or X86. This will build an optimized version of the gem5 binary (gem5.opt) for the the specified architecture. See http://www.gem5.org/documentation/general_docs/building for more details and options. The basic source release includes these subdirectories: - configs: example simulation configuration scripts - ext: less-common external packages needed to build gem5 - src: source code of the gem5 simulator - system: source for some optional system software for simulated systems - tests: regression tests - util: useful utility programs and files To run full-system simulations, you will need compiled system firmware (console and PALcode for Alpha), kernel binaries and one or more disk images. If you have questions, please send mail to gem5-users@gem5.org Enjoy using gem5 and please share your modifications and extensions.