A later patch removes boot_module and replaces its uses with bootmodule.
The equivalent field for "type" doesn't have BOOTMOD_UNKNOWN as a zero
value, so it must be explicitly set in the static xen_boot_info.
Not a functional change.
Signed-off-by: Alejandro Vallejo <agarc...@amd.com>
Reviewed-by: Stefano Stabellini <sstabell...@kernel.org>
---
xen/arch/x86/setup.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/xen/arch/x86/setup.c b/xen/arch/x86/setup.c
index 1f5cb67bd0..7d3b30e1db 100644
--- a/xen/arch/x86/setup.c
+++ b/xen/arch/x86/setup.c
@@ -298,6 +298,12 @@ struct boot_info __initdata xen_boot_info = {
.loader = "unknown",
.cmdline = "",
.domains = { [0 ... MAX_NR_BOOTDOMS - 1] = { .domid = DOMID_INVALID } },
+ /*
+ * There's a MAX_NR_BOOTMODS-th entry in the array. It's not off by one.
+ *
+ * The extra entry exists to be able to add the Xen image as a module.
+ */
+ .mods = { [0 ... MAX_NR_BOOTMODS] = { .type = BOOTMOD_UNKNOWN } },
};
static struct boot_info *__init multiboot_fill_boot_info(
--
2.43.0
