Re: [PATCH 1/2] kdump/x86: crashkernel=X try to reserve below 896M first then below 4G and MAXMEM

On 04/27/18 at 05:14pm, Dave Young wrote: > Hi, > > This is a resend of below patches: > http://lists.infradead.org/pipermail/kexec/2017-October/019569.html > > I dropped the original patch 1 since Baoquan is not happy with it. > For patch 2 (the 1st patch in this series), there is some improve

Re: [PATCH v9 02/11] kexec_file: make kexec_image_post_load_cleanup_default() global

On Tue, May 01, 2018 at 06:46:04PM +0100, James Morse wrote: > Hi Akashi, > > On 25/04/18 07:26, AKASHI Takahiro wrote: > > Change this function from static to global so that arm64 can implement > > its own arch_kimage_file_post_load_cleanup() later using > > kexec_image_post_load_cleanup_default(

Re: [PATCH v9 03/11] arm64: kexec_file: invoke the kernel without purgatory

On Tue, May 01, 2018 at 06:46:06PM +0100, James Morse wrote: > Hi Akashi, > > On 25/04/18 07:26, AKASHI Takahiro wrote: > > On arm64, purugatory would do almosty nothing. So just invoke secondary > > kernel directy by jumping into its entry code. > > (Nits: purgatory, almost, directly) Oops, I t

Re: [PATCH v9 04/11] arm64: kexec_file: allocate memory walking through memblock list

James, On Tue, May 01, 2018 at 06:46:09PM +0100, James Morse wrote: > Hi Akashi, > > On 25/04/18 07:26, AKASHI Takahiro wrote: > > We need to prevent firmware-reserved memory regions, particularly EFI > > memory map as well as ACPI tables, from being corrupted by loading > > kernel/initrd (or oth