sim: Create a Workload object for SE mode.
authorGabe Black <gabeblack@google.com>
Sun, 23 Aug 2020 06:33:10 +0000 (23:33 -0700)
committerGabe Black <gabeblack@google.com>
Sun, 20 Sep 2020 07:26:22 +0000 (07:26 +0000)
commit3293926413f84c4db4747537bf05c42a4c523c55
tree0a425ec1097d3e30bec14d4c6f0d7c143b74c14e
parentadb13e4fc7e2ca57dc828dfb22540da51b2b1aa2
sim: Create a Workload object for SE mode.

The workload object is still optional for the sake of compatibility,
even though it probably shouldn't be in the long term. If a simulation
is just a collection of components with nothing in particular running on
it, for instance driven by a traffic generator, should it even have a
System object in the first place?

Change-Id: I8bcda72bdfa3730248226fb62f0bba9a83243d95
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/33278
Reviewed-by: Matthew Poremba <matthew.poremba@amd.com>
Maintainer: Gabe Black <gabeblack@google.com>
Tested-by: kokoro <noreply+kokoro@google.com>
20 files changed:
configs/dram/low_power_sweep.py
configs/example/apu_se.py
configs/example/arm/starter_se.py
configs/example/hmc_hello.py
configs/example/se.py
configs/learning_gem5/part1/simple.py
configs/learning_gem5/part1/two_level.py
configs/learning_gem5/part2/simple_cache.py
configs/learning_gem5/part2/simple_memobj.py
configs/learning_gem5/part3/simple_ruby.py
configs/splash2/cluster.py
configs/splash2/run.py
src/sim/SConscript
src/sim/System.py
src/sim/Workload.py
src/sim/se_workload.cc [new file with mode: 0644]
src/sim/se_workload.hh [new file with mode: 0644]
tests/configs/gpu-ruby.py
tests/gem5/cpu_tests/run.py
tests/gem5/m5threads_test_atomic/atomic_system.py