GitLab

For SimBricks messages sent by gem5, we want the simulation to look like it started at tick 0. The reason is that otherwise, after restoring a checkpoint, connected simulators first have to catch up, i.e. simulate until the checkpoint tick before the simulation can continue.

The solution here was quite hacky in that we modified gem5's checkpoint file to have a timestamp of 0. This actually breaks when simulating a Linux host and conducting time measurements. The numbers you get will end up all over the place.

Add width and height attribute in the top-level svg tag. This also fixes the logo not showing up in our documentation.

This prevents gem5 from erroring out after closing and re-opening VS Code.

Our VS Code devcontainer is based on our buildenv container, so we directly modify the latter.

We needed it to ensure that gem5's `PerfKvmCounter::attach()` would work but with simbricks/simbricks#109 this has become unnecessary.

This includes adding a requirements.txt for the Python packages required for linting. In the future, additional packages that our orchestration framework requires also go in here.

* dist/common/base: fix taking member of packed struct warning

* trace: removed outdated folder

* lib/simbricks/nicbm/multinic: fixed boost bind warning

* sims/net/pktgen/pktgen: removed forward_pkt and potential use

This removes automatically sorting the keys that I introduced in #97, which means that instead, attributes are serialized in the order they are defined in. With this change, simple information like start and end time are readable at a glance directly at the top of the JSON file.

This is based on our recent HackerNews Post and the description on our website.

allows callers to add a name suffix for each connection, so there are separate unix sockets.