Re: [PATCH v5 00/16] kexec: introduce Kexec HandOver (KHO)

[Mike Rapoport]

On March 25, 2025 10:19:53 AM EDT, Pasha Tatashin <pasha.tatas...@soleen.com> 
wrote:
>> To use the code, please boot the kernel with the "kho=on" command line
>> parameter.
>> KHO will automatically create scratch regions. If you want to set the
>> scratch size explicitly you can use "kho_scratch=" command line parameter.
>> For instance, "kho_scratch=16M,512M,256M" will reserve a 16 MiB low
>> memory scratch area, a 512 MiB global scratch region, and 256 MiB
>> per NUMA node scratch regions on boot.
>
>kho_scratch= is confusing. It should be renamed to what this memory
>actually represents, which is memory that cannot be preserved by KHO.
>
>I suggest renaming all references to "scratch" and this parameter to:
>
>kho_nopersistent= or kho_nopreserve=

I'm leaning towards kho_bootstrap

>This way, we can also add checks that early allocations done by the
>kernel in this memory do not get preserved. We can also add checks to
>ensure that scarce low DMA memory does not get preserved across
>reboots, and we avoid adding fragmentation to that region.
>
>Pasha
>

-- 
Sincerely yours,
Mike