On 4/10/25 22:37, Changyuan Lyu wrote: > When the actual kexec happens, the fdt is part of the image > set that we boot into. In addition, we keep "scratch regions" available > for kexec: physically contiguous memory regions that are guaranteed to > not have any memory that KHO would preserve. The new kernel bootstraps > itself using the scratch regions and sets all handed over memory as in use. > When drivers initialize that support KHO, they introspect the fdt, restore > preserved memory regions, and retrieve their states stored in the preserved > memory.
It would be nice to have some bit of this blurb in the per-arch changelogs. It's not clear what the scratch regions are and how they are being used in the early boot code. Even a pointer over to the Documentation/ would be appreciated.
