Messages in this thread Patch in this message | | | From | AKASHI Takahiro <> | Subject | [PATCH v11 04/15] kexec_file: kexec_walk_memblock() only walks a dedicated region at kdump | Date | Wed, 11 Jul 2018 16:41:52 +0900 |
| |
In kdump case, there exists only one dedicated memoblock region as usable memory (crashk_res). With this patch, kexec_walk_memblock() runs a given callback function on this region.
Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org> Cc: Dave Young <dyoung@redhat.com> Cc: Vivek Goyal <vgoyal@redhat.com> Cc: Baoquan He <bhe@redhat.com> --- kernel/kexec_file.c | 3 +++ 1 file changed, 3 insertions(+)
diff --git a/kernel/kexec_file.c b/kernel/kexec_file.c index b088324fb3ad..ebf06c3e168d 100644 --- a/kernel/kexec_file.c +++ b/kernel/kexec_file.c @@ -511,6 +511,9 @@ static int kexec_walk_memblock(struct kexec_buf *kbuf, phys_addr_t mstart, mend; struct resource res = { }; + if (kbuf->image->type == KEXEC_TYPE_CRASH) + return func(&crashk_res, kbuf); + if (kbuf->top_down) { for_each_free_mem_range_reverse(i, NUMA_NO_NODE, 0, &mstart, &mend, NULL) { -- 2.17.0
| |