python: Move native wrappers to the _m5 namespace
Swig wrappers for native objects currently share the _m5.internal name space with Python code. This is undesirable if we ever want to switch from Swig to some other framework for native binding (e.g., PyBind11 or Boost::Python). This changeset moves all of such wrappers to the _m5 namespace, which is now reserved for native code. Change-Id: I2d2bc12dbc05b57b7c5a75f072e08124413d77f3 Signed-off-by: Andreas Sandberg <andreas.sandberg@arm.com> Reviewed-by: Curtis Dunham <curtis.dunham@arm.com> Reviewed-by: Jason Lowe-Power <jason@lowepower.com>
This commit is contained in:
@@ -36,6 +36,7 @@
|
||||
# Authors: Andreas Sandberg
|
||||
|
||||
import m5
|
||||
import _m5
|
||||
from m5.objects import *
|
||||
m5.util.addToPath('../configs/')
|
||||
from common.Caches import *
|
||||
@@ -104,7 +105,7 @@ def run_test(root, switcher=None, freq=1000, verbose=False):
|
||||
# Suppress "Entering event queue" messages since we get tons of them.
|
||||
# Worse yet, they include the timestamp, which makes them highly
|
||||
# variable and unsuitable for comparing as test outputs.
|
||||
m5.internal.core.cvar.want_info = verbose
|
||||
_m5.core.cvar.want_info = verbose
|
||||
|
||||
# instantiate configuration
|
||||
m5.instantiate()
|
||||
|
||||
Reference in New Issue
Block a user