gem5 - gem5

Age	Commit message (Collapse)	Author
2016-12-05	ruby: Remove RubyMemoryControl and associated files	Andreas Hansson
	This patch removes the deprecated RubyMemoryControl. The DRAMCtrl module should be used instead.
2014-01-10	ruby: move all statistics to stats.txt, eliminate ruby.stats	Nilay Vaish

2013-05-21	ruby: add stats to .sm files, remove cache profiler	Nilay Vaish ext:(%2C%20Malek%20Musleh%20%3Cmalek.musleh%40gmail.com%3E)
	This patch changes the way cache statistics are collected in ruby. As of now, there is separate entity called CacheProfiler which holds statistical variables for caches. The CacheMemory class defines different functions for accessing the CacheProfiler. These functions are then invoked in the .sm files. I find this approach opaque and prone to error. Secondly, we probably should not be paying the cost of a function call for recording statistics. Instead, this patch allows for accessing statistical variables in the .sm files. The collection would become transparent. Secondly, it would happen in place, so no function calls. The patch also removes the CacheProfiler class. --HG-- rename : src/mem/slicc/ast/InfixOperatorExprAST.py => src/mem/slicc/ast/OperatorExprAST.py
2011-08-08	BuildEnv: Eliminate RUBY as build environment variable	Nilay Vaish
	This patch replaces RUBY with PROTOCOL in all the SConscript files as the environment variable that decides whether or not certain components of the simulator are compiled.
2010-01-29	ruby: cleaned up ruby profilers	Brad Beckmann
	Cleaned up the ruby profilers by moving the memory controller profiling code out of the main profiler object and into a separate object similar to the current CacheProfiler. Both the CacheProfiler and MemCntrlProfiler are specific to a particular Ruby object, CacheMemory and MemoryControl respectively. Therefore, these profilers should not be SimObjects and created by the python configuration system, but instead private objects. This simplifies the creation of these profilers.
2010-01-29	ruby: Convert most Ruby objects to M5 SimObjects.	Steve Reinhardt
	The necessary companion conversion of Ruby objects generated by SLICC are converted to M5 SimObjects in the following patch, so this patch alone does not compile. Conversion of Garnet network models is also handled in a separate patch; that code is temporarily disabled from compiling to allow testing of interim code.
2009-05-11	ruby: add RUBY sticky option that must be set to add ruby to the build	Nathan Binkert
	Default is false
2009-05-11	ruby: Migrate all of ruby and slicc to SCons.	Nathan Binkert
	Add the PROTOCOL sticky option sets the coherence protocol that slicc will parse and therefore ruby will use. This whole process was made difficult by the fact that the set of files that are output by slicc are not easily known ahead of time. The easiest thing wound up being to write a parser for slicc that would tell me. Incidentally this means we now have a slicc grammar written in python.