On Thu, Nov 21, 2013 at 02:01:24PM -0700, Jerry Hoemann wrote: > > Some platform have firmware that violates the UEFI spec and access boot > service code or data segments after the system has called ExitBootServices(). > The call to efi_reserve_boot_services in setup_arch is a workaround to > avoid using boot service memory until after the kernel has done > SetVirtualAddressMap. However, this reservation fragments memory > which can cause large allocations early in boot (e.g. crash kernel) > to fail. This is a problem we have to solve, but I don't think this is the right way to solve it. Why do we not just reattempt to perform the allocation immediately after we've freed the boot services regions? -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
