[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5ace86cc-0b2d-4306-8bc1-dfc34cccef1a@redhat.com>
Date: Mon, 3 Nov 2025 13:08:38 +0100
From: David Hildenbrand <david@...hat.com>
To: Xie Yuanbin <xieyuanbin1@...wei.com>, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com, hpa@...or.com,
akpm@...ux-foundation.org, lorenzo.stoakes@...cle.com,
Liam.Howlett@...cle.com, vbabka@...e.cz, rppt@...nel.org, surenb@...gle.com,
mhocko@...e.com, linmiaohe@...wei.com, nao.horiguchi@...il.com,
luto@...nel.org, peterz@...radead.org, tony.luck@...el.com
Cc: x86@...nel.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-edac@...r.kernel.org, will@...nel.org, liaohua4@...wei.com,
lilinjie8@...wei.com
Subject: Re: [PATCH 1/2] x86/mm: support memory-failure on 32-bits with
SPARSEMEM
On 03.11.25 04:35, Xie Yuanbin wrote:
> The historical commit d949f36f1865c60239d4 ("x86: Fix hwpoison code
> related build failure on 32-bit NUMAQ"), disabled x86_32's
> memory-failure when SPARSEMEM is enabled, because the number of
> page-flags are insufficient.
>
> The commit 09022bc196d23484a7a5 ("mm: remove PG_error") removes a
> page flag, so memory-failure can now be enable now.
In the meantime, we added PG_dropbehind
--
Cheers
David / dhildenb
Powered by blists - more mailing lists