gem5 cache automate benchmarks, and remove results that were scattered all over.
Move console fun under linux kernel section, since not important enough
for getting started.
Set arch x86_64 by default through common on all scripts.
Document that X11 mouse is not moving.
Convert x='' to x= on all scripts, and also fix case ;; indentations.
Add dummy value to QEMU's -trace enable= to prevent warning.
Expand built-in package choice rationale.
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.
The error was:
[PARSEC] Error: Binary '/home/ciro/bak/git/linux-kernel-module-cheat/out/aarch64/buildroot/build/parsec-benchmark-custom/ext/splash2x/apps/barnes/inst/"aarch64"-linux.gcc/bin/run.sh' of package 'splash2x.barnes'
cannot be found.
due to some quoting madness.
Most of it was present inside buildroot/output.* and the rest scattered
on top level.
This came about for the n-th time when we were reviewing QEMU trace file
locations.
On one hand, it would be cool to have per arch traces.
This made buildroot/output.${arch}~/ a natural choice.
But on the other, those traces have nothing to do with Buildroot,
and could potentially interfere with Buildroot build files.
It also feels nicer to have buildroot/ pristine source code only,
and keep all output under a single directory out/
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.
This lead to a re-factoring of count boot instructions, since trace2line
relies on the same tracing mechanism.
Also, now that we have common factored, I've decided to put the traces on
the out dir, to concentrate all outputs in a single place, and allow
easy switching between archs.
We have wanted to do this since forever, but the last straw was gem5 aarch64,
which runs too fast, and makes it very hard to write "root" withing 60 seconds!
Another possibility to solve that would have been to find an answer for:
https://unix.stackexchange.com/questions/340333/how-can-i-get-bin-login-to-not-timeout
which we didn't, but not typing root at all is even better.
Take this opportunity to document how to login into user0.
sshd: automate and document further
gdbserver: automatically startup internet on /gdbserver.sh
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.
