gem5 - gem5

Age	Commit message (Collapse)	Author
2014-01-10	ruby: move all statistics to stats.txt, eliminate ruby.stats	Nilay Vaish

2013-02-19	scons: Add warning for missing declarations	Andreas Hansson
	This patch enables warnings for missing declarations. To avoid issues with SWIG-generated code, the warning is only applied to non-SWIG code.
2013-02-10	ruby: replaces Time with Cycles in many places	Nilay Vaish
	The patch started of with replacing Time with Cycles in the Consumer class. But to get ruby to compile, the rest of the changes had to be carried out. Subsequent patches will further this process, till we completely replace Time with Cycles.
2012-09-18	ruby: avoid using g_system_ptr for event scheduling	Nilay Vaish
	This patch removes the use of g_system_ptr for event scheduling. Each consumer object now needs to specify upfront an EventManager object it would use for scheduling events. This makes the ruby memory system more amenable for a multi-threaded simulation.
2012-08-27	Ruby: Remove RubyEventQueue	Nilay Vaish
	This patch removes RubyEventQueue. Consumer objects now rely on RubySystem or themselves for scheduling events.
2012-07-12	Ruby: remove config information from ruby.stats	Nilay Vaish
	This patch removes printConfig() functions from all structures in Ruby. Most of the information is already part of config.ini, and where ever it is not, it would become in due course.
2011-04-15	includes: sort all includes	Nathan Binkert

2011-03-31	CacheMemory: add allocateVoid() that is == allocate() but no return value.	Lisa Hsu
	This function duplicates the functionality of allocate() exactly, except that it does not return a return value. In protocols where you just want to allocate a block but do not want that block to be your implicitly passed cache_entry, use this function. Otherwise, SLICC will complain if you do not consume the pointer returned by allocate(), and if you do a dummy assignment Entry foo := cache.allocate(address), the C++ compiler will complain of an unused variable. This is kind of a hack to get around those issues, but suggestions welcome.
2011-03-31	Ruby: Add new object called WireBuffer to mimic a Wire.	Lisa Hsu
	This is a substitute for MessageBuffers between controllers where you don't want messages to actually go through the Network, because requests/responses can always get reordered wrt to one another (even if you turn off Randomization and turn on Ordered) because you are, after all, going through a network with contention. For systems where you model multiple controllers that are very tightly coupled and do not actually go through a network, it is a pain to have to write a coherence protocol to account for mixed up request/response orderings despite the fact that it's completely unrealistic. This is not meant as a substitute for real MessageBuffers when messages do in fact go over a network.