mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2025-05-03 05:56:57 +00:00
c74b1941a0
Previously sanitize_multiboot_info() was called after init_debug_pre() because the debug message can only print after uart is initialized. On the other hand, multiboot cmdline need to be parsed before init_debug_pre() because the cmdline could override uart settings and make sure debug message printed successfully. This cause multiboot info was parsed in two stages. The patch revise the multiboot parse logic that split sanitize_multiboot_info() api and use init_acrn_multiboot_info() api for the early stage. The most of multiboot info will be initialized during this stage and no debug message need to be printed. After uart is initialized, the sanitize_multiboot_info() would do sanitize multiboot info and print needed debug messages. Tracked-On: #4885 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Yin Fengwei <fengwei.yin@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
82 lines
2.1 KiB
C
82 lines
2.1 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>
|
|
|
|
#define MAX_BOOTARGS_SIZE 2048U
|
|
#define MAX_MODULE_COUNT 4U
|
|
|
|
/* 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_COUNT];
|
|
|
|
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
|
|
|
|
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_ */
|