81355c4124
A huge problem with latency sensitive baremetal worklaods is interrupts being triggered spuriously. Unfortunately when we start with cloud images, often they default to logging to a serial console which means every write is an interrupt, which is far from ideal and can result in packet loss and service degredation quite quickly. So instead, if the console logging has been disabled, and no virtual terminal has been defined, we now strip the console entries from the resulting image. In testing with Centos9 Stream, with booting a VM, the console in this scenario jumps to the framebuffer once started, and after thousands of lines being written to the console, even with delays, locally I'm at 219 interrupts, with a bulk of the entries coming from before I interacted with the console (~135 from just boot). Change-Id: Id9b19c4d9804b88e6db05a20e26c8264bb357734
9 lines
347 B
YAML
9 lines
347 B
YAML
---
|
|
features:
|
|
- |
|
|
Adds logic to permit the removal of consoles when the bootloader element
|
|
when no configuration has been expressed which requests it, and serial
|
|
console is disabled. This involves ``DIB_BOOTLOADER_VIRTUAL_TERMINAL``
|
|
being set to an empty string and ``DIB_BOOTLOADER_USE_SERIAL_CONSOLE``
|
|
is set to ``False``.
|