On Wed, 02 Sep 2026 15:31:13 +0800, Wandun Chen wrote:
From: Wandun Chen <redacted>
Add a 'dumpable' flag to struct reserved_mem to decide whether a
reserved area should be included in the kdump vmcore. Non-dumpable
regions are later marked MEMBLOCK_NODUMP;the filtering itself happens
in memblock, keeping the arch kdump code independent of the DT API.
Most reserved regions are owned by devices and do not contain data
useful for kernel crash analysis, so dumpable default to false.
Reusable CMA regions are different: their pages are handed back to the
buddy allocator and may contain key data for crash analysis, so set
dumpable to true in rmem_cma_setup().
The dumpable flag is also used to check /memreserve/ entries for overlap
with other dumpable regions.
Suggested-by: Rob Herring <robh@kernel.org>
Signed-off-by: Wandun Chen <redacted>
Tested-by: Meijing Zhao <redacted>
Acked-by: Marek Szyprowski <m.szyprowski@samsung.com>
---
include/linux/of_reserved_mem.h | 1 +
kernel/dma/contiguous.c | 1 +
2 files changed, 2 insertions(+)
Acked-by: Rob Herring (Arm) <robh@kernel.org>