|
@@ -333,7 +333,7 @@ void __init efi_reserve_boot_services(void)
|
|
|
|
|
|
/*
|
|
/*
|
|
* Because the following memblock_reserve() is paired
|
|
* Because the following memblock_reserve() is paired
|
|
- * with free_bootmem_late() for this region in
|
|
|
|
|
|
+ * with memblock_free_late() for this region in
|
|
* efi_free_boot_services(), we must be extremely
|
|
* efi_free_boot_services(), we must be extremely
|
|
* careful not to reserve, and subsequently free,
|
|
* careful not to reserve, and subsequently free,
|
|
* critical regions of memory (like the kernel image) or
|
|
* critical regions of memory (like the kernel image) or
|
|
@@ -364,7 +364,7 @@ void __init efi_reserve_boot_services(void)
|
|
* doesn't make sense as far as the firmware is
|
|
* doesn't make sense as far as the firmware is
|
|
* concerned, but it does provide us with a way to tag
|
|
* concerned, but it does provide us with a way to tag
|
|
* those regions that must not be paired with
|
|
* those regions that must not be paired with
|
|
- * free_bootmem_late().
|
|
|
|
|
|
+ * memblock_free_late().
|
|
*/
|
|
*/
|
|
md->attribute |= EFI_MEMORY_RUNTIME;
|
|
md->attribute |= EFI_MEMORY_RUNTIME;
|
|
}
|
|
}
|
|
@@ -414,7 +414,7 @@ void __init efi_free_boot_services(void)
|
|
size -= rm_size;
|
|
size -= rm_size;
|
|
}
|
|
}
|
|
|
|
|
|
- free_bootmem_late(start, size);
|
|
|
|
|
|
+ memblock_free_late(start, size);
|
|
}
|
|
}
|
|
|
|
|
|
if (!num_entries)
|
|
if (!num_entries)
|