只读Kexec交接模式 · v1

Expose the physical address of the outgoing KHO FDT via /sys/kernel/debug/kho/out/fdt_phys (analogous to bootmem_phys) so that userspace tooling can locate the root KHO FDT in physical memory. Also a

Move the shared KHO radix tree key encoding and indexing helpers, vmalloc flag conversion helpers, and FDT validation and lookup helpers from kexec_handover.c into kexec_handover_internal.h as static

kho_restore_vmalloc() currently dereferences preservation before checking for NULL, does not reject unknown KHO vmalloc flags in kho_flags_to_vmalloc(), and does not validate preservation->first.phys,

When restoring an incoming block set via kho_block_set_restore(), the physical chain of blocks is already linked and bs->head_pa is already set. However, kho_block_add() unconditionally rewrites last-

[kho: add read-only Kexec Handover mode] [patchwork series v1] submitter=Pasha Tatashin patches (8): [v1,1/8] kho: expose physical address of outgoing FDT [v1,2/8] kho: move radix tree, vmalloc, a

In read-only KHO mode, incoming serialized kho_block chains lie outside the kernel’s direct map and must not be modified or freed back into the page allocator. Map incoming serialized blocks read-onl

Allow CONFIG_TEST_KEXEC_HANDOVER to be enabled with CONFIG_KEXEC_HANDOVER_READONLY and update test_kho to verify preserved state when booted in read-only KHO mode. In read-only mode, test_kho retriev

Extend tools/testing/selftests/kho/vmtest.sh and init.c to run a second QEMU test verifying read-only KHO (‘kho_ro=<fdt_phys>’) after the standard KHO test on both x86_64 and aarch64: - Build a secon