GitLab

So far, simulator instances not connected to any other instances were
skipped accidentally when creating the graph.

Currently, when a checkpoint is created in gem5 using the KVM CPU, the
simulated tick when the checkpoint is taken will end up in the few
seconds or more when the KVM CPU is slow. When the checkpoint is
afterwards restored, gem5 will continue the simulation at this tick.
This means that other, synchronized simulators first have to catch up,
essentially just synchronizing without performing any useful work.
Depending on their speed, this can take a lot of time and is especially
costly with a RTL simulator in the loop. To avoid this we now, by
default, edit the to be restored gem5 checkpoint to start at tick 0
instead.

Add a cleanup script for ns-3 similar to those for qemu and gem5.

This solves #9.

When we switched to a newer kernel version in c64d3d0e, the
cleanup_images.sh script no longer removed the linux kernel source
folder, since it still used the old version number. Now, I use a regex
to avoid this issue in the future.

There are now no more inline functions and a proper main function
instead of top-level code. Functionality-wise, nothing was changed. Code
was only rearranged and some comments added.

hot-fix for #75 but temporarliy breaks experiments that use Simics. We will fix
this in a later commit.

Starting with Python3.11, asyncio.wait() doesn't accept coroutines anymore. Instead, we have to wrap every coroutine in a tasks.

this flag was added added only recently which produces an error when used, for example, on Debian 12

Add new target `clean-external` to the Makefile, which triggers the
clean task of the respective buid system for each external simulator.
Each simulator can also be cleaned individually by using the targets
`{simulator name}-clean` (e.g. `gem5-clean`).

`make distclean` now actually removes the external simulators

- change example experiment to pyexps/simple_ping.py
- quickstart.rst: remove repeated information already found in README
- README: add note that simbricks-run is only available in docker containers

- add `Error Opening images/output-base/base.raw`
- move `Getting Help` to the beginning and add content