From: Catalin Marinas <catalin.marinas@arm.com>
To: Shyam Saini <shyamsaini@linux.microsoft.com>
Cc: Mike Rapoport <rppt@kernel.org>,
ardb@kernel.org, david@kernel.org, will@kernel.org,
linux-arm-kernel@lists.infradead.org, akpm@linux-foundation.org,
bboscaccy@linux.microsoft.com, bp@alien8.de,
dapeng1.mi@linux.intel.com, ebiggers@kernel.org,
elver@google.com, enelsonmoore@gmail.com,
feng.tang@linux.alibaba.com, gpiccoli@igalia.com,
kees@kernel.org, kuba@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
lirongqing@baidu.com, peterz@infradead.org,
rdunlap@infradead.org, tgopinath@linux.microsoft.com,
tony.luck@intel.com, Lorenzo Pieralisi <lpieralisi@kernel.org>,
Hanjun Guo <guohanjun@huawei.com>,
Sudeep Holla <sudeep.holla@kernel.org>
Subject: Re: [RFC v2 PATCH] reserve_mem: add support for static memory
Date: Wed, 8 Jul 2026 11:00:27 +0100 [thread overview]
Message-ID: <ak4fu1qINGyAQUEl@arm.com> (raw)
In-Reply-To: <20260630170911.43521-1-shyamsaini@linux.microsoft.com>
Hi Shyam,
Adding Lorenzo, Hanjun, Sudeep.
On Tue, Jun 30, 2026 at 10:09:11AM -0700, Shyam Saini wrote:
> Following up on this, As Mike pointed that reserve_mem is best effort
> reservation mechanism, so what is the recommended reliable Linux
> mechanism, if any, to reserve a predetermined memory range during
> early boot on ARM64/ACPI platforms for warm boot scenarios? KHO is
> one option, but I'm specifically looking for a solution that preserves
> the region across warm reboots.
If you need ramoops-like support, I think ACPI ERST is a better fit and
we don't need any memory reservation tricks. I'll let the arm ACPI
maintainers comment further.
--
Catalin
next prev parent reply other threads:[~2026-07-08 10:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 6:23 [RFC v2 PATCH] reserve_mem: add support for static memory Shyam Saini
2026-06-19 18:35 ` Randy Dunlap
2026-06-25 1:09 ` Shyam Saini
2026-06-21 10:36 ` Mike Rapoport
2026-06-25 1:22 ` Shyam Saini
2026-06-25 8:37 ` Mike Rapoport
2026-06-26 14:54 ` Shyam Saini
2026-06-30 17:09 ` Shyam Saini
2026-07-08 10:00 ` Catalin Marinas [this message]
2026-07-09 0:37 ` Shyam Saini
2026-07-09 10:26 ` Sudeep Holla
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=ak4fu1qINGyAQUEl@arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=bboscaccy@linux.microsoft.com \
--cc=bp@alien8.de \
--cc=dapeng1.mi@linux.intel.com \
--cc=david@kernel.org \
--cc=ebiggers@kernel.org \
--cc=elver@google.com \
--cc=enelsonmoore@gmail.com \
--cc=feng.tang@linux.alibaba.com \
--cc=gpiccoli@igalia.com \
--cc=guohanjun@huawei.com \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lirongqing@baidu.com \
--cc=lpieralisi@kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=shyamsaini@linux.microsoft.com \
--cc=sudeep.holla@kernel.org \
--cc=tgopinath@linux.microsoft.com \
--cc=tony.luck@intel.com \
--cc=will@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox