configs,tests: use Sequencer port connect methods
authorTiago Mück <tiago.muck@arm.com>
Sat, 20 Jun 2020 02:08:33 +0000 (21:08 -0500)
committerTiago Mück <tiago.muck@arm.com>
Mon, 7 Dec 2020 19:52:22 +0000 (19:52 +0000)
commitca29eef37e010c6c5e02a212302a799f7fb5a37d
tree6ca3c580249f3ce1671b5e994db85c90d2a89f7a
parent4f4853012965e74fa420ffabaae4d1bdf3c2fd83
configs,tests: use Sequencer port connect methods

This patch updates Ruby configuration scripts to use the functions
defined in the RubySequencer python object to connect to cpu ports.

Only the protocol-agnostic scripts were updated. Scripts that assume
a specific protocol (e.g. configs/example/apu_se.py, gpu tests, etc)
and scripts in which the obj connected to the RubySequencer is not a
BaseCPU (e.g. the tests scripts) were not changed as they require a
non-standard port wireup.

Change-Id: I1e931ff0fc93f393cb36fbb8769ea4b48e1a1e86
Signed-off-by: Tiago Mück <tiago.muck@arm.com>
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/31418
Reviewed-by: Jason Lowe-Power <power.jg@gmail.com>
Maintainer: Jason Lowe-Power <power.jg@gmail.com>
Tested-by: kokoro <noreply+kokoro@google.com>
configs/example/fs.py
configs/example/se.py
configs/learning_gem5/part3/msi_caches.py
configs/learning_gem5/part3/ruby_caches_MI_example.py
configs/ruby/Ruby.py
tests/configs/pc-simple-timing-ruby.py