On 25/09/2025 19:03, Jan Beulich wrote:
> On 25.09.2025 16:56, Oleksii Moisieiev wrote:
>> This commit introduces a new Kconfig option, `CONFIG_DOM0_BOOT`, to
>> allow for building Xen without support for booting a regular domain (Dom0).
>> This functionality is primarily intended for the ARM architecture.
>>
>> A new Kconfig symbol, `HAS_DOM0`, has been added and is selected by
>> default for ARM and X86 architecture. This symbol signifies that an
>> architecture has the capability to support a Dom0.
>>
>> The `DOM0_BOOT` option depends on `HAS_DOM0` and defaults to 'y'. For
>> expert users, this option can be disabled (`CONFIG_EXPERT=y` and no
>> `CONFIG_DOM0_BOOT` in the config), which will compile out the Dom0
>> creation code on ARM. This is useful for embedded or dom0less-only
>> scenarios to reduce binary size and complexity.
>>
>> The ARM boot path has been updated to panic if it detects a non-dom0less
>> configuration while `CONFIG_DOM0_BOOT` is disabled, preventing an invalid
>> boot.
>>
>> Signed-off-by: Oleksii Moisieiev <[email protected]>
>>
>> ---
>>
>> Changes in v4:
>> - change Misra rule to 2.1 from 2.2 in description
>> - remove extra dependencies for ARM architecture from DOM0_BOOT
>> - rephrase DOM0_BOOT help by adding hyperlaunch
>> - DOM0_BOOT is not mandatory for x86 architecture
> Luckily this is merely wrong here ("not" should be dropped), but correct
> in the actual Kconfig logic, so:
> Acked-by: Jan Beulich <[email protected]>
>
> Jan
Yeah, I had word "now" in mind while typing this...
Oleksii
