Nilay Vaish 0811f21f67 ruby: provide a backing store ... Ruby's functional accesses are not guaranteed to succeed as of now. While this is not a problem for the protocols that are currently in the mainline repo, it seems that coherence protocols for gpus rely on a backing store to supply the correct data. The aim of this patch is to make this backing store configurable i.e. it comes into play only when a particular option: --access-backing-store is invoked. The backing store has been there since M5 and GEMS were integrated. The only difference is that earlier the system used to maintain the backing store and ruby's copy was write-only. Sometime last year, we moved to data being supplied supplied by ruby in SE mode simulations. And now we have patches on the reviewboard, which remove ruby's copy of memory altogether and rely completely on the system's memory to supply data. This patch adds back a SimpleMemory member to RubySystem. This member is used only if the option: access-backing-store is set to true. By default, the memory would not be accessed.		2014-11-06 05:42:21 -06:00
..
MESI_Three_Level.py	ruby: interface with classic memory controller	2014-11-06 05:42:21 -06:00
MESI_Two_Level.py	ruby: interface with classic memory controller	2014-11-06 05:42:21 -06:00
MI_example.py	ruby: interface with classic memory controller	2014-11-06 05:42:21 -06:00
MOESI_CMP_directory.py	ruby: interface with classic memory controller	2014-11-06 05:42:21 -06:00
MOESI_CMP_token.py	ruby: interface with classic memory controller	2014-11-06 05:42:21 -06:00
MOESI_hammer.py	ruby: interface with classic memory controller	2014-11-06 05:42:21 -06:00
Network_test.py	ruby: single physical memory in fs mode	2014-11-06 05:41:44 -06:00
Ruby.py	ruby: provide a backing store	2014-11-06 05:42:21 -06:00