From: Breno Leitao <leitao@debian.org>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Baoquan He <baoquan.he@linux.dev>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Miaohe Lin <linmiaohe@huawei.com>,
Naoya Horiguchi <nao.horiguchi@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org, rmikey@meta.com, riel@surriel.com,
kernel-team@meta.com, Kiryl Shutsemau <kas@kernel.org>
Subject: Re: [PATCH v2] kexec: keep the next kernel off hardware-poisoned pages
Date: Fri, 31 Jul 2026 11:11:01 -0700 [thread overview]
Message-ID: <amzkmjkJtLyYnE-y@gmail.com> (raw)
In-Reply-To: <2vxzecgj6od4.fsf@kernel.org>
On Fri, Jul 31, 2026 at 07:49:27PM +0200, Pratyush Yadav wrote:
> > + * return phys_addr_t, thus this "extra" parameter, instead of returning
> > + * the hit.
> > + */
> > +bool range_contains_hwpoison(phys_addr_t start, unsigned long size,
> > + phys_addr_t *poison)
>
> Perhaps
>
> phys_addr_t range_last_hwpoison(phys_addr_t start, unsigned long size) ?
>
> And if no poisoned page lands here then a default of 0 or ~0UL?
That was my initial preference, but hypothetically phys_addr_t 0 could be
a poisoned page.
I hadn't considered ~0UL as a sentinel — that should work and is a good
suggestion. let me prototype.
Thanks for the review.
--breno
prev parent reply other threads:[~2026-07-31 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 15:55 [PATCH v2] kexec: keep the next kernel off hardware-poisoned pages Breno Leitao
2026-07-30 16:18 ` Breno Leitao
2026-07-31 17:49 ` Pratyush Yadav
2026-07-31 18:11 ` Breno Leitao [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=amzkmjkJtLyYnE-y@gmail.com \
--to=leitao@debian.org \
--cc=akpm@linux-foundation.org \
--cc=baoquan.he@linux.dev \
--cc=david@kernel.org \
--cc=kas@kernel.org \
--cc=kernel-team@meta.com \
--cc=kexec@lists.infradead.org \
--cc=liam@infradead.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=nao.horiguchi@gmail.com \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=riel@surriel.com \
--cc=rmikey@meta.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@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.