4d7384e9df
The original implementation of curTick used a thread local variable, _curEventQueue, and its getCurTick() method, to retrieve the curTick for the currently active event queue. That meant that core.hh needed to include eventq.hh so that the EventQueue type was available, which also indirectly brought in a lot of other dependencies. Unfortunately this couldn't easily be fixed by making curTick() non-inline since this added a significant amount of overhead when tested. Instead, this change makes the code in core.hh/core.cc keep a pointer directly to a Tick. The code which sets _curEventQueue now also sets that pointer when _curEventQueue changes. The way curTick() now reaches into the guts of the current EventQueue directly is not great from a modularity perspective, but if curTick is considered an extension of the EventQueue, then it's just odd that this part is broken out into a different file. Change-Id: I8341b40fe75e90672eb1d70e1a368975fcbfe926 Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/38996 Maintainer: Gabe Black <gabe.black@gmail.com> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Daniel Carvalho <odanrc@yahoo.com.br> Reviewed-by: Jason Lowe-Power <power.jg@gmail.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.