Victor Sun 28824c1e74 HV: init e820 before init paging ... In the commit of 4e1deab3d9, we changed the init sequence that init paging first and then init e820 because we worried about the efi memory map could be beyond 4GB space on some platform. After we double checked multiboot2 spec, when system boot from multiboot2 protocol, the efi memory map info will be embedded in multiboot info so it is guaranteed that the efi memory map must be under 4GB space. Consider that the page table will be allocated in free memory space in future, we have to change the init sequence back that init e820 first and then init paging. If we need to support other boot protocol in future that the efi memory map might be put beyond 4GB, we could have below options: 1. Request bootloader put efi memory map below 4GB; 2. Call EFI_BOOT_SERVICES.GetMemoryMap() before ExitBootServices(); 3. Enable a early 64bit page table to get the efi memory map only; Tracked-On: #5626 Signed-off-by: Victor Sun <victor.sun@intel.com>		2021-09-27 09:03:15 +08:00
..
guest	HV: Add implements of 32bit and 64bit elf loader	2021-08-19 20:00:45 +08:00
include	HV: Add elf loader sketch	2021-08-19 20:00:45 +08:00
multiboot	HV: init e820 before init paging	2021-09-27 09:03:15 +08:00
acpi_base.c	HV: modularization: rename mi_acpi_rsdp_va to acpi_rsdp_va	2021-06-11 10:06:02 +08:00
boot.c	HV: init e820 before init paging	2021-09-27 09:03:15 +08:00
reloc.c	hv: mod: do not use explicit arch name when including headers	2021-05-08 11:15:46 +08:00