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.
Automatically pick up packages from under packages/ into BR2_EXTERNAL.
Move many subdirectory READMEs into the toplevel and link to toplevel from those subreadmes instead.
Split optional and required kernel configs into separate files.
readme: describe how our kernel configs are generated from Buildroot
readme: document QEMU `-no-reboot` and speculate gem5 `panic_on_panic`
in preparation for some more automated bisection with ktest.
gem5 requires armv7, and we learnt that the versatiledb we were using
was pre-v7.
We could have moved to -M vexpress-*, but in the end decided to go for
-M virt due to its simpliciy, and uniformity with aarch64.
platform_device: does not work anymore and was removed, since it was tied
to versatilepb.
We left a mention on the README and removed all in tree source. The QEMU
patch is still left as it was.
As a consequence, the linux tree had no other patches, and we now use
vanilla linux by default, which is a great thing for reproducibility.
Another consequence is the /poweroff.out works for arm -M virt,
and we removed all mentions of the problem.
This is cleaner as it removes yet another .gitignore rule and allows
for one command per arch.
This was prompted by the recent Docker patch creating files as root,
which then breaks future host runs.
Also separate all arguments by newlines. This:
- makes it much easier to minimize when reporting QEMU bugs
- shows the full command on the screen despite line wrapping being turned off
by one of the annoying emulators, to be investigated.
The commands are not yet pristine, because:
- there are some leading spaces
- options not sorted
but it is already a huge improvement, and those operations are now be easy from Vim.
The general strategy is:
- end every variable containing a command with a newline
- when expanding such variables, don't add an extra newline
Someone was trying to build on a 1 core machine and it broke the build.
The rationale for the -2 was to leave 2 cores for your to use your computer still,
but let us trust the OS scheduler a bit more.
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.
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/
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.
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.
