5eb4f5fe11
In order to have more fine grained control over which SLICC controllers are part of which Ruby network in a disjoint configuration, the create_system function in GPU_VIPER is broken up into multiple construct calls for each SLICC machine type in the protocol. By default this does not change anything functionally. A future config will use the construct calls to explicitly set which network (CPU or GPU) the controller is in. Change-Id: Ic038b300c5c3732e96992ef4bfe14e43fa0ea824 Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/51847 Reviewed-by: Jason Lowe-Power <power.jg@gmail.com> Reviewed-by: Matt Sinclair <mattdsinclair@gmail.com> Maintainer: Jason Lowe-Power <power.jg@gmail.com> Tested-by: kokoro <noreply+kokoro@google.com>