Reuses the module system dependencies present there.
run: make --dry-run work even when there is no out directory yet
docker: make the wrapping more intuitive
This way we group key value arguments: e.g.:
make \
-j 8 \
all
instead of:
make \
-j \
8 \
all
and reach CLI nirvana, while also subtly breaking several commands due to
lack of testing.
Unsquashed version at v2-rc-unsquashed, but that cannot be merged as it
breaks bisects at several points. All bugs will not bisect to this
humongous change.
It all started with a conversion of the Bash scripts to Python, mainly
because I couldn't stand not being able to properly use --options for
run which has a million options.
Then since that required a full testing, I decided to do all the
refactorings that I had in mind at once, and so I did and it became
v2-rc.
This is the largest patch I have ever done! OMG a few weeks of extra time.
I'm never writing a Bash script for anything that starts getting big again.
Some of the features are:
* separate build-qemu and build-gem5 commands
* common: convert scripts to python. Add --option for everything
* rename build to build-buildroot now that we are splitting all the build
commands, Linux kernel to follow
* move all git submodules to submodules/ and all buildroot packages to
packages/
* refactor the out/ structure. Keep projects on toplevel, because guest
projects separate archs and host ones don't, making a toplevel arch wrong
* do-release: rename to just release
https://stackoverflow.com/questions/16174992/cant-get-argparse-to-read-quoted-string-with-dashes-in-it
* run: add --terminal and explain gem5 pdb
* just track the lvimrc
* store CLI kernel config fragment inside buildlroot to avoid conflicts
* gem5: document m5 initparam
* readme: make a bunch of things awesomer
* readme: fix broken refs
* parsec-benchmark: update to 75d55ac446a43c47efb1044844a108c6c330184c
Could not fetch otherwise.
* gem5: M5_OVERRIDE_PY_SOURCE
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.
