This is a squash commit, the unsquashed development went through many
unstable phases which would break bisects. The unsquashed branch is:
https://github.com/cirosantilli/linux-kernel-module-cheat/tree/v3.0-unsquash
The main improvement of this release was to greatly generalize the testing system.
The key addition was cli_function.py, which allows scripts such as ./run to
be transparently called either from Python or from the command line.
New tests scripts were created using this improved framework: test-baremetal
and test-user-mode.
We were lazy to port some of less important tests to the new setup, TODO's were
added, and we need comes they will be fixed. Getting started is however sacred
as usual and should work.
Other changes include:
- gem5: update to 7fa4c946386e7207ad5859e8ade0bbfc14000d91
- run: --tmux-args implies --tmux
- run: add --userland-args to make userland arguments across QEMU and gem5
Get rid of --userland-before as a consequence.
- bring initrd and initramfs back to life
- build-userland: create --static to make build a bit easier
- gem5: --gem5-worktree also set --gem5-build-id
- remove --gem5, use --emulator gem5 everywhere
Allow passing --emulator multiple times for transparent tests selection
just like --arch.
- test-userland: allow selecting just a few tests
- linux: update to v4.20
- buildroot: update to 2018.08
The main motivation for this was to fix the build for Ubuntu 18.10, which
has glibc 2.28, which broke the 2018.05 build at the m4-host package with:
#error "Please port gnulib fseeko.c to your platform!
- getvar --type input
- failed xen attempt, refactor timer, failed svc attempt, aarch64 use gicv3
- build-doc: exit 1 on error, add to release testing
- build: add --apt option to make things easier on other distros
- build-linux: --no-modules-install
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/
Semi automated conversion, in part because Pandoc is kind of buggy for adoc:
Some of the commands were along the lines:
for f in *.md; do pandoc --atx-headers --base-header-level=3 -o ${f%.md}.adoc --wrap=none $f; done
sed -Ei '/\[\[.*\]\]/d' *.adoc
while read -r f; do cat $f; echo; done <f >g
