Do not perform cache flushing in clearMemory. Instead flush the cache
only for those object types where it is necessary, and only when the
object is retyped, not when the untyped cap is reset.

This reduces overall need for flushing and delays it to the point of
use. This should speed up boot time significantly, but may impact WCET,
because the largest flush is now the largest page size (e.g. 24) instead
of CONFIG_RESET_CHUNK_BITS (8). The user could already request a flush
of the largest page size before, though, so it this may not actually
impact WCET. Remains to be investigated.

Why this is safe:

- Flushing is only necessary for objects that are seen by other parts of
  the system, not for kernel-internal object. These objects are
  non-device frames (including IOMMU pages) and page tables. All other
  objects are only read/written by the kernel. Frames need to be flushed
  to RAM (as clearMemory did), because they could be seen uncached by
  devices. Page tables only to PoU for the page table walker.

- Before createNewObject in retype, these objects do not exist and
  cannot be seen by any part of the system. createNewObject is the point
  where new objects can become visible to the user.

- Theoretically, we could defer flushing further to the point where
  frames or page tables are mapped, but it is more complex to track
  whether a flush has already happened when they are mapped multiple
  times, whereas at retype the object cannot have been flushed already.

- The original implementation, before clearing memory was moved into
  reset untyped, also flushed at the same points.

Signed-off-by: Gerwin Klein <[email protected]>

The function expects the size in bits.

Signed-off-by: Axel Heider <[email protected]>

The AARCH64 config now also works for functional correctness on
zcu102/zcu106 and rpi4.

Signed-off-by: Gerwin Klein <[email protected]>

Signed-off-by: Axel Heider <[email protected]>

- unify benchmarking across all architectures
- drop global variables ksExit, ksLogIndexFinalized
- improve comments

Signed-off-by: Axel Heider <[email protected]>

- cleanup includes and guards
- hide includes if features are not enabled.
- improve comments

Signed-off-by: Axel Heider <[email protected]>

Remove ksUserLogBuffer declaration from the state data and declare it in
the benchmark code instead.

Signed-off-by: Axel Heider <[email protected]>

add ENABLE_KERNEL_TRACEPOINTS

Signed-off-by: Axel Heider <[email protected]>

Signed-off-by: Axel Heider <[email protected]>

Signed-off-by: Axel Heider <[email protected]>

Signed-off-by: Axel Heider <[email protected]>

- define core specific timestampEnter
- remove generic ksExit

Signed-off-by: Axel Heider <[email protected]>

Signed-off-by: Axel Heider <[email protected]>

Rename CONFIG_KERNEL_LOG_BUFFER to CONFIG_ENABLE_KERNEL_LOG_BUFFER to
follow the logic used already for other automatically generated config
settings.

Signed-off-by: Axel Heider <[email protected]>

Signed-off-by: Axel Heider <[email protected]>