From: Pratyush Yadav <pratyush@kernel.org>
To: Shyam Saini <shyamsaini@linux.microsoft.com>
Cc: linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, rppt@kernel.org,
akpm@linux-foundation.org, kees@kernel.org,
tony.luck@intel.com, gpiccoli@igalia.com, bp@alien8.de,
rdunlap@infradead.org, peterz@infradead.org,
feng.tang@linux.alibaba.com, dapeng1.mi@linux.intel.com,
elver@google.com, enelsonmoore@gmail.com, kuba@kernel.org,
lirongqing@baidu.com, ebiggers@kernel.org
Subject: Re: [RFC PATCH] reserve_mem: add support for static memory
Date: Tue, 23 Jun 2026 15:10:32 +0200 [thread overview]
Message-ID: <2vxzpl1hmmgn.fsf@kernel.org> (raw)
In-Reply-To: <20260618224018.117978-1-shyamsaini@linux.microsoft.com> (Shyam Saini's message of "Thu, 18 Jun 2026 15:40:18 -0700")
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@linux.microsoft.com>
[...]
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2026-06-23 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 22:40 [RFC PATCH] reserve_mem: add support for static memory Shyam Saini
2026-06-18 23:02 ` Randy Dunlap
2026-06-23 13:10 ` Pratyush Yadav [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2vxzpl1hmmgn.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dapeng1.mi@linux.intel.com \
--cc=ebiggers@kernel.org \
--cc=elver@google.com \
--cc=enelsonmoore@gmail.com \
--cc=feng.tang@linux.alibaba.com \
--cc=gpiccoli@igalia.com \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lirongqing@baidu.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=shyamsaini@linux.microsoft.com \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.