summaryrefslogtreecommitdiff
path: root/configs/ruby/GPU_VIPER.py
diff options
context:
space:
mode:
authorAndreas Hansson <andreas.hansson@arm.com>2016-10-13 03:17:19 -0400
committerAndreas Hansson <andreas.hansson@arm.com>2016-10-13 03:17:19 -0400
commit68fdccb30bd85cd99823fb411ec7ae67112062d7 (patch)
treee6ef3d54238c64c63b00a3b83da96a9a1cdaad8b /configs/ruby/GPU_VIPER.py
parent2e5e9085792b1a7c47c231a2adf0da6f7ff8f20d (diff)
downloadgem5-68fdccb30bd85cd99823fb411ec7ae67112062d7.tar.xz
ruby: Fix regressions and make Ruby configs Python packages
This patch moves the addition of network options into the Ruby module to avoid the regressions all having to add it explicitly. Doing this exposes an issue in our current config system though, namely the fact that addtoPath is relative to the Python script being executed. Since both example and regression scripts use the Ruby module we would end up with two different (relative) paths being added. Instead we take a first step at turning the config modules into Python packages, simply by adding a __init__.py in the configs/ruby, configs/topologies and configs/network subdirectories. As a result, we can now add the top-level configs directory to the Python search path, and then use the package names in the various modules. The example scripts are also updated, and the messy path-deducing variations in the scripts are unified.
Diffstat (limited to 'configs/ruby/GPU_VIPER.py')
-rw-r--r--configs/ruby/GPU_VIPER.py4
1 files changed, 2 insertions, 2 deletions
diff --git a/configs/ruby/GPU_VIPER.py b/configs/ruby/GPU_VIPER.py
index eeed637d4..e4ba18089 100644
--- a/configs/ruby/GPU_VIPER.py
+++ b/configs/ruby/GPU_VIPER.py
@@ -40,8 +40,8 @@ from m5.defines import buildEnv
from Ruby import create_topology
from Ruby import send_evicts
-from Cluster import Cluster
-from Crossbar import Crossbar
+from topologies.Cluster import Cluster
+from topologies.Crossbar import Crossbar
class CntrlBase:
_seqs = 0