Messages in this thread | | | From | Thiago Jung Bauermann <> | Subject | Re: [RESEND PATCH v5 06/11] ppc64/kexec_file: restrict memory usage of kdump kernel | Date | Mon, 27 Jul 2020 23:10:08 -0300 |
| |
Hari Bathini <hbathini@linux.ibm.com> writes:
> Kdump kernel, used for capturing the kernel core image, is supposed > to use only specific memory regions to avoid corrupting the image to > be captured. The regions are crashkernel range - the memory reserved > explicitly for kdump kernel, memory used for the tce-table, the OPAL > region and RTAS region as applicable. Restrict kdump kernel memory > to use only these regions by setting up usable-memory DT property. > Also, tell the kdump kernel to run at the loaded address by setting > the magic word at 0x5c. > > Signed-off-by: Hari Bathini <hbathini@linux.ibm.com> > Tested-by: Pingfan Liu <piliu@redhat.com>
I liked the new versions of get_node_path_size() and get_node_path().
Reviewed-by: Thiago Jung Bauermann <bauerman@linux.ibm.com>
-- Thiago Jung Bauermann IBM Linux Technology Center
| |