From: Xie Yuanbin <xieyuanbin1@huawei.com>
To: <david@kernel.org>, <dave.hansen@intel.com>
Cc: <Liam.Howlett@oracle.com>, <akpm@linux-foundation.org>,
<bp@alien8.de>, <dave.hansen@linux.intel.com>, <hpa@zytor.com>,
<liaohua4@huawei.com>, <lilinjie8@huawei.com>,
<linmiaohe@huawei.com>, <linux-edac@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<lorenzo.stoakes@oracle.com>, <luto@kernel.org>,
<mhocko@suse.com>, <mingo@redhat.com>, <nao.horiguchi@gmail.com>,
<peterz@infradead.org>, <rppt@kernel.org>, <surenb@google.com>,
<tglx@linutronix.de>, <tony.luck@intel.com>, <vbabka@suse.cz>,
<will@kernel.org>, <x86@kernel.org>, <xieyuanbin1@huawei.com>
Subject: Re: [PATCH v2 0/2] x86/mm: support memory-failure on 32-bits with SPARSEMEM
Date: Wed, 5 Nov 2025 17:05:36 +0800 [thread overview]
Message-ID: <20251105090536.11676-1-xieyuanbin1@huawei.com> (raw)
In-Reply-To: <57936358-69b0-4028-a0df-b5f5acc32ca9@kernel.org>
On Wed, 5 Nov 2025 09:12:04 +0100, Dave Hansen wrote:
> Let me clarify what we need to know:
>
> Will you (or your employer) be running such updated 32bit kernels on
> hardware that supports MCEs.
>
> In other words: is this change driver by *real demand*
Thanks! Asking like this, I completely understand now.
We won't directly upgrade the kernel to 6.18.x (or later versions) to use
this feature, but if Linux community approves these patches, we will
backport it to 5.10.x and use it. I know that the page-flags in 5.10.x
have been exhausted, but we can work around them by adjusting
SECTION_SIZE_BITS/MAX_PHYSMEM_BITS to free up a page flag.
Another patch I submitted for arm32:
Link: https://lore.kernel.org/20250922021453.3939-1-xieyuanbin1@huawei.com
, follows the same logic.
Currently, there is a clear demand for ARM32, while the demand for x86 is
still under discussion.
> or just by "oh
> look, we can enable that now, I can come up with a theoretical use case
> but I don't know if anybody would actually care"?
It can also be said that way. In fact, when developing the demand
"support MEMORY_FAILURE for 32-bit OS" in version 5.10.x, I found that the
latest version already supported this feature, so I submitted these
patches, and hope others can benefit from it as well.
> Cheers
>
> David
Thanks!
Xie Yuanbin
next prev parent reply other threads:[~2025-11-05 9:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 7:23 Xie Yuanbin
2025-11-04 7:23 ` [PATCH v2 1/2] " Xie Yuanbin
2025-11-04 7:23 ` [PATCH v2 2/2] mm/memory-failure: remove the selection of RAS Xie Yuanbin
2025-11-04 9:38 ` David Hildenbrand (Red Hat)
2025-11-04 9:50 ` Xie Yuanbin
2025-11-04 9:33 ` [PATCH v2 0/2] x86/mm: support memory-failure on 32-bits with SPARSEMEM David Hildenbrand (Red Hat)
2025-11-04 13:29 ` Xie Yuanbin
2025-11-04 13:32 ` Xie Yuanbin
2025-11-04 14:26 ` Dave Hansen
2025-11-05 2:45 ` Xie Yuanbin
2025-11-05 8:12 ` David Hildenbrand (Red Hat)
2025-11-05 9:05 ` Xie Yuanbin [this message]
2025-11-17 2:09 ` Xie Yuanbin
2025-11-17 13:03 ` David Hildenbrand (Red Hat)
2025-11-18 8:09 ` Xie Yuanbin
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=20251105090536.11676-1-xieyuanbin1@huawei.com \
--to=xieyuanbin1@huawei.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=hpa@zytor.com \
--cc=liaohua4@huawei.com \
--cc=lilinjie8@huawei.com \
--cc=linmiaohe@huawei.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=luto@kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=nao.horiguchi@gmail.com \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vbabka@suse.cz \
--cc=will@kernel.org \
--cc=x86@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