mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2025-05-02 05:34:04 +00:00
db690e0967
Previously the VM kernel bootargs for pre-launched VMs and direct boot mode of SOS VM are built-in hypervisor binary so end users have no way to change it. Now we provide another option that the multiboot module string could be used as bootargs also. This would bring convenience to end users when they use GRUB as bootloader because the bootargs could be configurable in GRUB menu. The usage is if there is any string follows configured kernel_mod_tag in module string, the string will be used as new kernel bootargs instead of built-in kernel bootargs. If there is no string follows kernel_mod_tag, then the built-in bootargs will be the default kernel bootargs. Please note kernel_mod_tag must be the first word in module string in any case, it is used to specify the module for which VM. Tracked-On: #4885 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Yin Fengwei <fengwei.yin@intel.com> Reviewed-by: Eddie Dong <eddie.dong@intel.com>
89 lines
2.5 KiB
C
89 lines
2.5 KiB
C
/*
|
|
* Copyright (C) 2020 Intel Corporation. All rights reserved.
|
|
*
|
|
* SPDX-License-Identifier: BSD-3-Clause
|
|
*/
|
|
|
|
#ifndef BOOT_H_
|
|
#define BOOT_H_
|
|
|
|
#include <multiboot.h>
|
|
#ifdef CONFIG_MULTIBOOT2
|
|
#include <multiboot2.h>
|
|
#endif
|
|
#include <e820.h>
|
|
#include <zeropage.h>
|
|
#include <vm_configurations.h>
|
|
|
|
#define MAX_BOOTARGS_SIZE 2048U
|
|
/* The modules in multiboot are for kernel and ramdisk of pre-launched VMs and SOS VM */
|
|
#define MAX_MODULE_NUM (2U * PRE_VM_NUM + 2U * SOS_VM_NUM)
|
|
|
|
/* extended flags for acrn multiboot info from multiboot2 */
|
|
#define MULTIBOOT_INFO_HAS_EFI_MMAP 0x00010000U
|
|
#define MULTIBOOT_INFO_HAS_EFI64 0x00020000U
|
|
|
|
struct acrn_multiboot_info {
|
|
uint32_t mi_flags; /* the flags is back-compatible with multiboot1 */
|
|
|
|
const char *mi_cmdline;
|
|
const char *mi_loader_name;
|
|
|
|
uint32_t mi_mods_count;
|
|
const void *mi_mods_va;
|
|
struct multiboot_module mi_mods[MAX_MODULE_NUM];
|
|
|
|
uint32_t mi_drives_length;
|
|
uint32_t mi_drives_addr;
|
|
|
|
uint32_t mi_mmap_entries;
|
|
const void *mi_mmap_va;
|
|
struct multiboot_mmap mi_mmap_entry[E820_MAX_ENTRIES];
|
|
|
|
const void *mi_acpi_rsdp_va;
|
|
struct efi_info mi_efi_info;
|
|
};
|
|
|
|
/* boot_regs store the multiboot info magic and address */
|
|
extern uint32_t boot_regs[2];
|
|
|
|
extern char *efiloader_sig;
|
|
|
|
static inline bool boot_from_multiboot1(void)
|
|
{
|
|
return ((boot_regs[0] == MULTIBOOT_INFO_MAGIC) && (boot_regs[1] != 0U));
|
|
}
|
|
|
|
#ifdef CONFIG_MULTIBOOT2
|
|
/*
|
|
* @post boot_regs[1] stores the address pointer that point to a valid multiboot2 info
|
|
*/
|
|
static inline bool boot_from_multiboot2(void)
|
|
{
|
|
/*
|
|
* Multiboot spec states that the Multiboot information structure may be placed
|
|
* anywhere in memory by the boot loader.
|
|
*
|
|
* Seems both SBL and GRUB won't place multiboot1 MBI structure at 0 address,
|
|
* but GRUB could place Multiboot2 MBI structure at 0 address until commit
|
|
* 0f3f5b7c13fa9b67 ("multiboot2: Set min address for mbi allocation to 0x1000")
|
|
* which dates on Dec 26 2019.
|
|
*/
|
|
return (boot_regs[0] == MULTIBOOT2_INFO_MAGIC);
|
|
}
|
|
|
|
int32_t multiboot2_to_acrn_mbi(struct acrn_multiboot_info *mbi, void *mb2_info);
|
|
#endif
|
|
|
|
/*
|
|
* The extern declaration for acrn_mbi is for cmdline.c use only, other functions should use
|
|
* get_multiboot_info() API to access struct acrn_mbi because it has explict @post condition
|
|
*/
|
|
extern struct acrn_multiboot_info acrn_mbi;
|
|
struct acrn_multiboot_info *get_multiboot_info(void);
|
|
void init_acrn_multiboot_info(void);
|
|
int32_t sanitize_multiboot_info(void);
|
|
void parse_hv_cmdline(void);
|
|
|
|
#endif /* BOOT_H_ */
|