test-baremetal: create

README.adoc

@@ -3157,9 +3157,9 @@ Result on <<p51>> at bad30f513c46c1b0995d3a10c0d9bc2a33dc4fa0:
 * QEMU user: 45 seconds
 * QEMU full system: 223 seconds
 
-=== User mode testing
+=== User mode tests
 
-Automatically run non-interactive userland tests that don't depend on nay kernel modules:
+Automatically run non-interactive userland tests that don't depend on any kernel modules:
 
 ....
 ./build-userland --all-archs --all-emulators
@@ -10897,6 +10897,23 @@ We then found out that QEMU starts in EL1, and so we kept just the EL1 part, and
 * https://stackoverflow.com/questions/42824706/qemu-system-aarch64-entering-el1-when-emulating-a53-power-up
 * https://stackoverflow.com/questions/37299524/neon-support-in-armv8-system-mode-qemu
 
+=== Baremetal tests
+
+Automatically run non-interactive baremetal tests:
+
+....
+./test-baremetal
+....
+
+Source: link:test-baremetal[]
+
+Since there is no standardized exit status concept that works across all emulators, we detect if tests failed by parsing logs for the string output by our fail function: `common_assert_fail()`.
+
+We also skip tests that cannot work on certain conditions based on their basenames, e.g.:
+
+* tests that start with `gem5_` only run in `gem5`
+* tests that start with `semihost_` only run in QEMU, until we find a better way to automate <<gem5-semihosting>>
+
 === Baremetal bibliography
 
 https://stackoverflow.com/questions/43682311/uart-communication-in-gem5-with-arm-bare-metal