[PATCH v4 1/2] LoongArch: kexec: use core control page for relocation trampoline to avoid QEMU FDT conflict
George Guo
dongtai.guo at linux.dev
Wed Jul 1 08:59:56 PDT 2026
From: George Guo <guodongtai at kylinos.cn>
KEXEC_CONTROL_CODE was hardcoded to TO_CACHE(0x100000). QEMU places its
machine FDT at physical 0x100000 when booting with '-kernel', so
machine_kexec_prepare() overwrote the FDT with the relocation trampoline.
The kexec'd kernel's fdt_setup() then read trampoline code instead of a
valid FDT, earlycon auto-detection failed, and the second kernel booted
silently with no console output.
The trampoline does not need a fixed address. It is executed by the
current kernel to relocate and enter the new kernel, and is dead once the
new kernel starts. Drop KEXEC_CONTROL_CODE and reuse the
control_code_page that the kexec core already allocates (as arm64 and
riscv do). That page is excluded from the relocation copy and lives
nowhere near 0x100000, so the QEMU FDT is left intact.
Signed-off-by: George Guo <guodongtai at kylinos.cn>
---
arch/loongarch/kernel/machine_kexec.c | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/arch/loongarch/kernel/machine_kexec.c b/arch/loongarch/kernel/machine_kexec.c
index ced49194d9de..7ced6ca2dadb 100644
--- a/arch/loongarch/kernel/machine_kexec.c
+++ b/arch/loongarch/kernel/machine_kexec.c
@@ -21,8 +21,6 @@
#include <asm/cacheflush.h>
#include <asm/page.h>
-/* 0x100000 ~ 0x200000 is safe */
-#define KEXEC_CONTROL_CODE TO_CACHE(0x100000UL)
#define KEXEC_CMDLINE_ADDR TO_CACHE(0x108000UL)
static unsigned long reboot_code_buffer;
@@ -76,9 +74,14 @@ int machine_kexec_prepare(struct kimage *kimage)
}
}
- /* kexec/kdump need a safe page to save reboot_code_buffer */
- kimage->control_code_page = virt_to_page((void *)KEXEC_CONTROL_CODE);
-
+ /*
+ * kexec/kdump need a safe page to save reboot_code_buffer. Reuse the
+ * control_code_page allocated by the kexec core (as arm64 and riscv
+ * do) instead of a fixed address: the trampoline is only executed by
+ * the current kernel before entering the new kernel, so it needs no
+ * fixed or reserved location. This also stops machine_kexec_prepare()
+ * from overwriting QEMU's machine FDT at 0x100000.
+ */
reboot_code_buffer = (unsigned long)page_address(kimage->control_code_page);
memcpy((void *)reboot_code_buffer, relocate_new_kernel, relocate_new_kernel_size);
--
2.25.1
More information about the kexec
mailing list