summaryrefslogtreecommitdiff
path: root/tests/quick/se/00.hello
diff options
context:
space:
mode:
authorNilay Vaish <nilay@cs.wisc.edu>2014-11-06 05:42:21 -0600
committerNilay Vaish <nilay@cs.wisc.edu>2014-11-06 05:42:21 -0600
commit0811f21f67493a77b0c5a69260715d7cce7341e7 (patch)
treea2d5bd98ccb5fa17637ff791f66184d220e0e341 /tests/quick/se/00.hello
parent3022d463fbe1f969aadf7284ade996539c9454f9 (diff)
downloadgem5-0811f21f67493a77b0c5a69260715d7cce7341e7.tar.xz
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.
Diffstat (limited to 'tests/quick/se/00.hello')
0 files changed, 0 insertions, 0 deletions