gem5/configs
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
..
boot rcs scripts: remove bbench.rcS 2013-04-02 12:46:49 -04:00
common ruby: interface with classic memory controller 2014-11-06 05:42:21 -06:00
dram mem: Rename Bus to XBar to better reflect its behaviour 2014-09-20 17:18:32 -04:00
example ruby: interface with classic memory controller 2014-11-06 05:42:21 -06:00
ruby ruby: provide a backing store 2014-11-06 05:42:21 -06:00
splash2 mem: Rename Bus to XBar to better reflect its behaviour 2014-09-20 17:18:32 -04:00
topologies config: topologies: slight code refactor 2014-02-23 19:16:15 -06:00