From: Kiryl Shutsemau <kas@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: Ard Biesheuvel <ardb@kernel.org>,
nao.horiguchi@gmail.com, linmiaohe@huawei.com, david@kernel.org,
lance.yang@linux.dev, akpm@linux-foundation.org,
baoquan.he@linux.dev, rppt@kernel.org, pratyush@kernel.org,
kexec@lists.infradead.org, linux-mm@kvack.org, rneu@meta.com,
riel@surriel.com, caggio@meta.com
Subject: Re: mm/hwpoison: persist poisoned PFN list across kexec via KHO [RFC]
Date: Wed, 24 Jun 2026 16:34:08 +0100 [thread overview]
Message-ID: <ajv4f4_m2rQ3hpoW@thinkstation> (raw)
In-Reply-To: <ajvzUg8KK9gtFTYe@gmail.com>
On Wed, Jun 24, 2026 at 08:21:16AM -0700, Breno Leitao wrote:
> > > Possible solutions
> > > ==================
> > ...
> > >
> > > 2. e820 / EFI memory map (E820_TYPE_UNUSABLE). Tempting because the
> > > frame would simply never become RAM (no allocator race at all).
> > > But: it is x86-only (no arm64 equivalent in the same mechanism;
> > > this series is tested on arm64);
> >
> > (+Ard. I might get some details around EFI wrong.)
> >
> > This isn't accurate, and I think it's the right direction for EFI
> > platforms. EFI_UNUSABLE_MEMORY is honored on both arches today, no new
> > consumer code:
> >
> > - arm64: reserve_regions() marks non-usable memory nomap.
>
> Is it true for non-UEFI arm64 hosts?
No. It is EFI-only thingy.
Is there non-EFI server platforms worth caring about?
--
Kiryl Shutsemau / Kirill A. Shutemov
next prev parent reply other threads:[~2026-06-24 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 10:39 mm/hwpoison: persist poisoned PFN list across kexec via KHO [RFC] Breno Leitao
2026-06-24 12:04 ` Kiryl Shutsemau
2026-06-24 13:46 ` Pratyush Yadav
2026-06-24 15:21 ` Breno Leitao
2026-06-24 15:34 ` Kiryl Shutsemau [this message]
2026-06-24 13:40 ` Pratyush Yadav
2026-06-24 14:44 ` Rik van Riel
2026-06-24 15:17 ` Pratyush Yadav
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=ajv4f4_m2rQ3hpoW@thinkstation \
--to=kas@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=baoquan.he@linux.dev \
--cc=caggio@meta.com \
--cc=david@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=lance.yang@linux.dev \
--cc=leitao@debian.org \
--cc=linmiaohe@huawei.com \
--cc=linux-mm@kvack.org \
--cc=nao.horiguchi@gmail.com \
--cc=pratyush@kernel.org \
--cc=riel@surriel.com \
--cc=rneu@meta.com \
--cc=rppt@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 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.