Make the debug tests aware of multicore.
authorTim Newsome <tim@sifive.com>
Mon, 7 Aug 2017 19:51:42 +0000 (12:51 -0700)
committerTim Newsome <tim@sifive.com>
Mon, 28 Aug 2017 19:16:39 +0000 (12:16 -0700)
commit3a44725d27f6b2c77f0ca912d792b6856fde6a17
treee89d52105aa01d59e7d4588ef157d477f0a4335d
parentab6c2ccaec192684cf4649d5d69bd105d738d1c7
Make the debug tests aware of multicore.

Targets now contain an array of harts. When running a regular test, one
hart is selected to run the test on while the remaining harts are parked
in a safe infinite loop.

There's currently only one test that tests multicore behavior, but there
could be more.

The infrastructure should be able to support heterogeneous multicore,
but I don't have a target like that to test with.
18 files changed:
debug/Makefile
debug/gdbserver.py
debug/programs/entry.S
debug/programs/start.S [deleted file]
debug/targets.py
debug/targets/RISC-V/spike.cfg [new file with mode: 0644]
debug/targets/RISC-V/spike32-2.py [new file with mode: 0644]
debug/targets/RISC-V/spike32.cfg [deleted file]
debug/targets/RISC-V/spike32.py
debug/targets/RISC-V/spike64-2.py [new file with mode: 0644]
debug/targets/RISC-V/spike64.cfg [deleted file]
debug/targets/RISC-V/spike64.py
debug/targets/SiFive/Freedom/E300.py
debug/targets/SiFive/Freedom/E300Sim.py
debug/targets/SiFive/Freedom/U500.py
debug/targets/SiFive/Freedom/U500Sim.py
debug/targets/SiFive/HiFive1.py
debug/testlib.py