From: Kiryl Shutsemau <k.shutemov@gmail.com>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Harry Yoo <harry@kernel.org>,
David Rientjes <rientjes@google.com>,
Amit Shah <amit@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Aneesh Kumar <AneeshKumar.KizhakeVeetil@arm.com>,
Christoph Lameter <christoph@gentwo.org>,
Dave Hansen <dave.hansen@intel.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Hugh Dickins <hughd@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
John Hubbard <jhubbard@nvidia.com>,
Matthew Wilcox <willy@infradead.org>,
Mel Gorman <mel.gorman@gmail.com>,
Michal Hocko <mhocko@suse.com>,
Mike Rapoport <mike.rapoport@gmail.com>,
Peter Xu <peterx@redhat.com>, Raghavendra K T <rkodsara@amd.com>,
"Rao, Bharata Bhasker" <bharata@amd.com>,
Rik van Riel <riel@surriel.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Shivank Garg <shivankg@amd.com>,
Sterling Alexander <stalexan@redhat.com>,
Suren Baghdasaryan <surenb@google.com>, Tejun Heo <tj@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>,
Yang Shi <shy828301@gmail.com>, Zi Yan <ziy@nvidia.com>,
William Roche <william.roche@oracle.com>,
linmiaohe@huawei.com, ljs@kernel.org, osalvador@kernel.org,
nao.horiguchi@gmail.com, tony.luck@intel.com,
wangkefeng.wang@huawei.com, jane.chu@oracle.com,
muchun.song@linux.dev, liam@infradead.org, shuah@kernel.org,
boudewijn@delta-utec.com, linux-mm@kvack.org,
Breno Leitao <leitao@debian.org>
Subject: Re: [Invitation] Linux MM Alignment Session on Hwpoison on Wednesday
Date: Thu, 24 Sep 2026 12:19:53 +0100 [thread overview]
Message-ID: <arUDeFDdSV1xANiU@thinkstation> (raw)
In-Reply-To: <6c79bc6c-abb7-407d-84cb-c9ab29732646@kernel.org>
On Thu, Sep 24, 2026 at 12:55:10PM +0200, David Hildenbrand (Arm) wrote:
> On 9/24/26 12:46, Kiryl Shutsemau wrote:
> > On Thu, Sep 24, 2026 at 10:32:29AM +0200, David Hildenbrand (Arm) wrote:
> >> On 9/23/26 16:36, Harry Yoo wrote:
> >>>
> >>> I believe this is what the patchset actually did in v2.
> >>>
> >>> That way we'll have to either
> >>> 1) make any architecture that supports kexec select ARCH_KEEP_MEMBLOCK,
> >>> or 2) make kexec scan the bitmap when allocating the memory.
> >>
> >> My naive design would be:
> >>
> >> 1) Teach memblock early about poisoned memory ranges. Don't let it hand them out.
> >
> > I suggested using a bitmap because ranges are not scalable. Some memory
> > failure modes generate errors repeated across the physical address space
> > (think of a column failure, for instance). It would produce too many
> > ranges to be viable.
>
> These are in 2M granularity. Is that a real problem?
2M is arbitrary. We can trade finer granularity for the size of the bitmap.
> > We already consult a bitmap in memblock for unaccepted memory. We *can*
> > do the same for poisoned memory.
> >
>
> We can do many things. I don't want it.
What's wrong with it? The last step on allocation from memblock check if
the memory is poisoned in bitmap. If it is, try again next range,
starting from the next non-poisoned address.
--
Kiryl Shutsemau / Kirill A. Shutemov
next prev parent reply other threads:[~2026-09-24 11:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 16:26 [Invitation] Linux MM Alignment Session on Hwpoison on Wednesday David Rientjes
2026-09-23 12:57 ` Harry Yoo
2026-09-23 13:37 ` David Hildenbrand (Arm)
2026-09-23 14:36 ` Harry Yoo
2026-09-24 8:32 ` David Hildenbrand (Arm)
2026-09-24 10:46 ` Kiryl Shutsemau
2026-09-24 10:55 ` David Hildenbrand (Arm)
2026-09-24 11:19 ` Kiryl Shutsemau [this message]
2026-09-24 11:23 ` David Hildenbrand (Arm)
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=arUDeFDdSV1xANiU@thinkstation \
--to=k.shutemov@gmail.com \
--cc=AneeshKumar.KizhakeVeetil@arm.com \
--cc=akpm@linux-foundation.org \
--cc=amit@infradead.org \
--cc=bharata@amd.com \
--cc=boudewijn@delta-utec.com \
--cc=christoph@gentwo.org \
--cc=dave.hansen@intel.com \
--cc=dave@stgolabs.net \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=harry@kernel.org \
--cc=hughd@google.com \
--cc=jane.chu@oracle.com \
--cc=jhubbard@nvidia.com \
--cc=leitao@debian.org \
--cc=liam@infradead.org \
--cc=linmiaohe@huawei.com \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mel.gorman@gmail.com \
--cc=mhocko@suse.com \
--cc=mike.rapoport@gmail.com \
--cc=muchun.song@linux.dev \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@kernel.org \
--cc=peterx@redhat.com \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=rkodsara@amd.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=shivankg@amd.com \
--cc=shuah@kernel.org \
--cc=shy828301@gmail.com \
--cc=stalexan@redhat.com \
--cc=surenb@google.com \
--cc=tj@kernel.org \
--cc=tony.luck@intel.com \
--cc=vbabka@kernel.org \
--cc=wangkefeng.wang@huawei.com \
--cc=william.roche@oracle.com \
--cc=willy@infradead.org \
--cc=ziy@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox