On 23.07.2025 16:05, 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 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 <oleksii_moisie...@epam.com>
Oh, also - can you please avoid Cc-ing (or even having as To: as you had
it here) email addresses that will reject replies (see attached)?
Jan
--- Begin Message ---
** Address not found **
Your message wasn't delivered to amd-xen-saf...@groups.io because the address
couldn't be found, or is unable to receive mail.
Learn more here: https://groups.io/g/amd-xen-safety
(Warning: This link will take you to a third-party site)
The response from the remote server was:
510 5.1.1 Your email address, jbeul...@suse.com, is not subscribed to that
group. To subscribe, send an email to amd-xen-safety+subscr...@groups.io, or
visit https://groups.io/g/amd-xen-safety
Reporting-MTA: dns; googlemail.com
Received-From-MTA: dns; jbeulich@suse.com
Arrival-Date: Wed, 23 Jul 2025 07:27:26 -0700 (PDT)
X-Original-Message-ID: <60627444-420d-42a1-b7b6-d74dec2479e0@suse.com>
Final-Recipient: rfc822; amd-xen-safety@groups.io
Action: failed
Status: 5.1.1
Remote-MTA: dns; lb02.groups.io. (173.255.221.194, the server for the domain groups.io.)
Diagnostic-Code: smtp; 510 5.1.1 Your email address, jbeulich@suse.com, is not subscribed to that group. To subscribe, send an email to amd-xen-safety+subscribe@groups.io, or visit https://groups.io/g/amd-xen-safety
Last-Attempt-Date: Wed, 23 Jul 2025 07:27:29 -0700 (PDT)
--- Begin Message ---
On 23.07.2025 16:05, Oleksii Moisieiev wrote:
> --- a/xen/arch/arm/Kconfig
> +++ b/xen/arch/arm/Kconfig
> @@ -19,6 +19,7 @@ config ARM
> select HAS_ALTERNATIVE if HAS_VMAP
> select HAS_DEVICE_TREE
> select HAS_DOM0LESS
> + select HAS_DOM0
This wants to move one line up, for the set to remain sorted. But see below.
> --- a/xen/common/Kconfig
> +++ b/xen/common/Kconfig
> @@ -21,6 +21,14 @@ config DOM0LESS_BOOT
> Xen boot without the need of a control domain (Dom0), which could be
> present anyway.
>
> +config DOM0_BOOT
> + bool "Dom0 boot support" if EXPERT
> + depends on HAS_DOM0 && HAS_DEVICE_TREE && DOMAIN_BUILD_HELPERS
> + default y
> + help
> + Dom0 boot support enables Xen to boot to the control domain (Dom0) and
> + manage domU guests using the Xen toolstack with provided
> configurations.
What about non-Arm? x86 has a Dom0 too, but doesn't select HAS_DOM0. It
actually requires a Dom0 for now, so to me HAS_DOM0 is a misnomer. Maybe
HAS_OPTIONAL_DOM0?
> @@ -92,6 +100,9 @@ config HAS_DEVICE_TREE
> config HAS_DOM0LESS
> bool
>
> +config HAS_DOM0
> + bool
Same here as to sorting, no matter that ...
> config HAS_DIT # Data Independent Timing
> bool
>
... HAS_DOM0LESS and this one are misplaced with one another.
Jan
--- End Message ---
--- End Message ---
