Otherwise, checking out branches is too insane, as it does not
update the worktrees, even though the gem5/gem5 module was updated.
gem5: expose build types, document debug builds.
simultaneous runs: store stdout and stderr on a file to allow running
all from a single terminal on the background cleanly.
As noted however, it is potentially too slow to be useful.
run: unify gem5 and qemu tracing under -T
readme: overhaul tracing documentation from what I've learnt from trace2line
Get rid of br2_parsec, since there are just too many possible variations on that file.
Blow up the gem5 vs qemu table to make it saner, add missing aarch64 entries.
Make sections titles describing number of cores and memory size emulator agnostic.
Otherwise it was getting messy to distinguish between trace-events
and trace-<pid> in the .gitignore.
Now only the latest trace will be kept, with a fixed name.
In order to make the system easier to understand.
These include:
* networking
* klogd and syslogd. TODO what are those for? I could not see anything useful that they do.
Also get rid of the useless S20random thing while we are at it.
This is necessary because qemu and gem5 now use the same build folder.
Separate ./run -e and -f for kernel options before and after the ' - '.
This was already the better thing to do when -E was introduced,
but lkmc_nonet prompted me to do it nicer now.
Use the common script to find the out_dir on every toplevel script.
Include usage man pages on README.