On Sat, Mar 04, 2023 at 11:09:11AM +0800, Youling Tang wrote:
> On LoongArch, we can use the same kernel image as 1st kernel when
> 3f89765d622 ("LoongArch: kdump: Add single kernel image implementation")
> is merged, but we have to modify the entry point as well as segments
> addresses in the
On Sat, Mar 04, 2023 at 11:09:10AM +0800, Youling Tang wrote:
> The initial reason is that after the merger of 29fe5067ed07 ("kexec: make
> -a the default"), kexec cannot be used on LoongArch architectures. We need
> to add "-c" for normal use. The current kexec_file_load system call is not
>
On Mon, Mar 06, 2023 at 04:41:24PM +0800, Baoquan He wrote:
> On arm64, reservation for 'crashkernel=xM,high' is taken by searching for
> suitable memory region top down. If the 'xM' of crashkernel high memory
> is reserved from high memory successfully, it will try to reserve
> crashkernel low
On Tue, Mar 07, 2023 at 04:44:16PM -0600, Bjorn Helgaas wrote:
> From: Bjorn Helgaas
>
> arch_kexec_kernel_image_load() only calls kexec_image_load_default(), and
> there are no arch-specific implementations.
>
> Remove the unnecessary arch_kexec_kernel_image_load() and make
>
On Tue, Mar 07, 2023 at 04:44:15PM -0600, Bjorn Helgaas wrote:
> From: Bjorn Helgaas
>
> The x86 implementation of arch_kexec_kernel_image_load() is functionally
> identical to the generic arch_kexec_kernel_image_load():
>
> arch_kexec_kernel_image_load# x86
> if