* [PATCH] arm64: kdump: fix out of memory issue in __alloc_bootmem_low
@ 2018-05-20 12:20 Chen Zhou
2018-05-21 11:45 ` Robin Murphy
0 siblings, 1 reply; 2+ messages in thread
From: Chen Zhou @ 2018-05-20 12:20 UTC (permalink / raw)
To: linux-arm-kernel
From: Mao Wenan <maowenan@huawei.com>
On arm64 kdump capture kernel, ACPI runtime code and data are outside
of usable memory range and __alloc_bootmem_low may alloc memory below
4G. If we use "crashkernel=Y[@X]" and the start address is above 4G,
there will be out of memory.
In this patch, we get max_zone_dma_phys by memblock_start_of_DRAM
and __pa_symbol(_end).
Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
---
arch/arm64/mm/init.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
index 1b18b47..df4d212 100644
--- a/arch/arm64/mm/init.c
+++ b/arch/arm64/mm/init.c
@@ -223,7 +223,8 @@ static void __init reserve_elfcorehdr(void)
*/
static phys_addr_t __init max_zone_dma_phys(void)
{
- phys_addr_t offset = memblock_start_of_DRAM() & GENMASK_ULL(63, 32);
+ phys_addr_t offset = max(memblock_start_of_DRAM(), __pa_symbol(_end)) &
+ GENMASK_ULL(63, 32);
return min(offset + (1ULL << 32), memblock_end_of_DRAM());
}
--
1.8.3
^ permalink raw reply related [flat|nested] 2+ messages in thread* [PATCH] arm64: kdump: fix out of memory issue in __alloc_bootmem_low
2018-05-20 12:20 [PATCH] arm64: kdump: fix out of memory issue in __alloc_bootmem_low Chen Zhou
@ 2018-05-21 11:45 ` Robin Murphy
0 siblings, 0 replies; 2+ messages in thread
From: Robin Murphy @ 2018-05-21 11:45 UTC (permalink / raw)
To: linux-arm-kernel
On 20/05/18 13:20, Chen Zhou wrote:
> From: Mao Wenan <maowenan@huawei.com>
>
> On arm64 kdump capture kernel, ACPI runtime code and data are outside
> of usable memory range and __alloc_bootmem_low may alloc memory below
> 4G. If we use "crashkernel=Y[@X]" and the start address is above 4G,
> there will be out of memory.
>
> In this patch, we get max_zone_dma_phys by memblock_start_of_DRAM
> and __pa_symbol(_end).
Entering the crash kernel doesn't magically reconfigure interconnects
such that 32-bit DMA masters can suddenly address whatever physical
address range the kernel image happens to be loaded at. This change is
fundamentally incorrect.
Robin.
> Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
> ---
> arch/arm64/mm/init.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
> index 1b18b47..df4d212 100644
> --- a/arch/arm64/mm/init.c
> +++ b/arch/arm64/mm/init.c
> @@ -223,7 +223,8 @@ static void __init reserve_elfcorehdr(void)
> */
> static phys_addr_t __init max_zone_dma_phys(void)
> {
> - phys_addr_t offset = memblock_start_of_DRAM() & GENMASK_ULL(63, 32);
> + phys_addr_t offset = max(memblock_start_of_DRAM(), __pa_symbol(_end)) &
> + GENMASK_ULL(63, 32);
> return min(offset + (1ULL << 32), memblock_end_of_DRAM());
> }
>
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-05-21 11:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-05-20 12:20 [PATCH] arm64: kdump: fix out of memory issue in __alloc_bootmem_low Chen Zhou
2018-05-21 11:45 ` Robin Murphy
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox