Ruby: Remove CacheMsg class from SLICC
authorNilay Vaish <nilay@cs.wisc.edu>
Tue, 22 Mar 2011 11:41:54 +0000 (06:41 -0500)
committerNilay Vaish <nilay@cs.wisc.edu>
Tue, 22 Mar 2011 11:41:54 +0000 (06:41 -0500)
commit1764ebbf30cfd94eb7ccc618ade0d70049db000e
tree3c400317f716fcf50c996e9f4fb03980efd9cf3a
parent46cce440be4999cfdedebbf190c83570ba9f1b49
Ruby: Remove CacheMsg class from SLICC
The goal of the patch is to do away with the CacheMsg class currently in use
in coherence protocols. In place of CacheMsg, the RubyRequest class will used.
This class is already present in slicc_interface/RubyRequest.hh. In fact,
objects of class CacheMsg are generated by copying values from a RubyRequest
object.
23 files changed:
src/mem/protocol/MESI_CMP_directory-L1cache.sm
src/mem/protocol/MI_example-cache.sm
src/mem/protocol/MOESI_CMP_directory-L1cache.sm
src/mem/protocol/MOESI_CMP_token-L1cache.sm
src/mem/protocol/MOESI_hammer-cache.sm
src/mem/protocol/Network_test-cache.sm
src/mem/protocol/RubySlicc_Exports.sm
src/mem/protocol/RubySlicc_Profiler.sm
src/mem/protocol/RubySlicc_Types.sm
src/mem/ruby/profiler/AddressProfiler.cc
src/mem/ruby/profiler/AddressProfiler.hh
src/mem/ruby/profiler/Profiler.cc
src/mem/ruby/profiler/Profiler.hh
src/mem/ruby/recorder/TraceRecord.cc
src/mem/ruby/slicc_interface/RubyRequest.cc
src/mem/ruby/slicc_interface/RubyRequest.hh
src/mem/ruby/slicc_interface/RubySlicc_Profiler_interface.hh
src/mem/ruby/slicc_interface/RubySlicc_Util.hh
src/mem/ruby/system/CacheMemory.cc
src/mem/ruby/system/CacheMemory.hh
src/mem/ruby/system/DMASequencer.cc
src/mem/ruby/system/RubyPort.cc
src/mem/ruby/system/Sequencer.cc