start microbenchmarks section

README.adoc

@@ -16422,8 +16422,14 @@ Don't forget to explicitly rebuild PARSEC with:
 You may also want to test if your patches are still functionally correct inside of QEMU first, which is a faster emulator.
 * sell your soul, and compile natively inside the guest. We won't do this, not only because it is evil, but also because Buildroot explicitly does not support it: https://buildroot.org/downloads/manual/manual.html#faq-no-compiler-on-target ARM employees have been known to do this: https://github.com/arm-university/arm-gem5-rsk/blob/aa3b51b175a0f3b6e75c9c856092ae0c8f2a7cdc/parsec_patches/qemu-patch.diff
 
+=== Micro benchmarks
+
+It eventually has to come to that, hasn't it?
+
+* link:userland/gcc/busy_loop.c[] described at <<infinite-busy-loop>>
+
 [[userland-libs-directory]]
-==== userland/libs directory
+=== userland/libs directory
 
 Tests under link:userland/libs[] require certain optional libraries to be installed on the target, and are not built or tested by default, you must enable them with either:
 
@@ -16434,7 +16440,7 @@ Tests under link:userland/libs[] require certain optional libraries to be instal
 
 See for example <<blas>>.
 
-===== HDF5
+==== HDF5
 
 https://en.wikipedia.org/wiki/Hierarchical_Data_Format
 

path_properties.py

@@ -690,6 +690,7 @@ path_properties_tuples = (
                 'gcc': (
                     {**gnu_extension_properties, **{'cc_pedantic': False}},
                     {
+                        'busy_loop.c': {'baremetal': True},
                         'openmp.c': {'cc_flags': ['-fopenmp', LF]},
                     }
                 ),

userland/gcc/busy_loop.c

@@ -1,4 +1,6 @@
-/* https://cirosantilli.com/linux-kernel-module-cheat#compilers */
+/* https://cirosantilli.com/linux-kernel-module-cheat#micro-benchmarks
+ * https://cirosantilli.com/linux-kernel-module-cheat#infinite-busy-loop
+ * https://cirosantilli.com/linux-kernel-module-cheat#benchmark-emulators-on-userland-executables */
 
 #include <stdlib.h>