Re: [RFC PATCH] reserve_mem: add support for static memory

[Pratyush Yadav]

On Thu, Jun 18 2026, Shyam Saini wrote:

> reserve_mem relies on dynamic memory allocation, this limits the
> usecase where memory and its address is required to be preserved
> across the boots. Eg: ramoops memory reservation on ACPI platforms
>
> So add support to pass a pre-determined static address and reserve
> memory at this specified address. This enables use case like ramoops
> on ACPI platforms to reliably access ramoops region across the boots.

Doesn't memmap= do exactly this? How is this different?

I always thought the point of reserve_mem was that you _don't_ have to
provide an explicit address, one is chosen for your machine
automatically.

>
> Also skip parsing of "align" parameter when static address is passed.
>
> Example syntax for static address
>  reserve_mem=4M@0x1E0000000:oops ramoops.mem_name=oops
>
> Signed-off-by: Shyam Saini <shyamsaini@xxxxxxxxxxxxxxxxxxx>
[...]

-- 
Regards,
Pratyush Yadav