mem-ruby: GCN3 and VIPER integration
authorTuan Ta <qtt2@cornell.edu>
Fri, 4 May 2018 16:14:13 +0000 (12:14 -0400)
committerAnthony Gutierrez <anthony.gutierrez@amd.com>
Fri, 19 Jun 2020 20:32:54 +0000 (20:32 +0000)
commit18ebe62598e09771f58d555faaed6e3572cc4d14
treebd3d8d26c6a07f5d43cf6eae0fb076d50cd5a533
parent3ca404da175a66e0b958165ad75eb5f54cb5e772
mem-ruby: GCN3 and VIPER integration

This patch modifies the Coalescer and VIPER protocol to support memory
synchronization requests and write-completion responses that are
required by upcoming GCN3 implementation.

VIPER protocol is simplified to be a solely write-through protocol.

Change-Id: Iccfa3d749a0301172a1cc567c59609bb548dace6
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/29913
Reviewed-by: Anthony Gutierrez <anthony.gutierrez@amd.com>
Reviewed-by: Jason Lowe-Power <power.jg@gmail.com>
Reviewed-by: Bradford Beckmann <brad.beckmann@amd.com>
Maintainer: Anthony Gutierrez <anthony.gutierrez@amd.com>
Maintainer: Bradford Beckmann <brad.beckmann@amd.com>
Tested-by: kokoro <noreply+kokoro@google.com>
12 files changed:
src/mem/ruby/protocol/GPU_VIPER-TCC.sm
src/mem/ruby/protocol/GPU_VIPER-TCP.sm
src/mem/ruby/protocol/GPU_VIPER-msg.sm
src/mem/ruby/protocol/MOESI_AMD_Base-dir.sm
src/mem/ruby/protocol/MOESI_AMD_Base-msg.sm
src/mem/ruby/protocol/RubySlicc_Types.sm
src/mem/ruby/slicc_interface/RubyRequest.hh
src/mem/ruby/system/GPUCoalescer.cc
src/mem/ruby/system/GPUCoalescer.hh
src/mem/ruby/system/RubyPort.cc
src/mem/ruby/system/VIPERCoalescer.cc
src/mem/ruby/system/VIPERCoalescer.hh