From: Xie Yuanbin <xieyuanbin1@huawei.com>
To: <dave.hansen@intel.com>, <david@kernel.org>
Cc: <Liam.Howlett@oracle.com>, <akpm@linux-foundation.org>,
<bp@alien8.de>, <dave.hansen@linux.intel.com>, <david@redhat.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 10:45:23 +0800 [thread overview]
Message-ID: <20251105024523.14300-1-xieyuanbin1@huawei.com> (raw)
In-Reply-To: <47b3e8ba-bc95-41ce-be0a-ddfd1323bab3@intel.com>
On Tue, 4 Nov 2025 06:26:58 -0800, Dave Hansen wrote:
> Which LLM generated that for you, btw?
I wrote this myself; LLM just helped me with the translation. My English
isn't very good, so I apologize for any mistakes.
> I wanted to know _specifically_ what kind of hardware or 32-bit
> environment you wanted to support with this series, though.
I think I have explained it clearly enough in this email:
Link: https://lore.kernel.org/20251104133254.145660-1-xieyuanbin1@huawei.com
In simple terms, it refers to some old existing equipment and some
embedded devices. More specifically, it includes some routers, switches,
and similar devices. From what I know, there is no VM environment that
using it.
If you are asking about a specific CPU chip model, I'm sorry, but I may
not be able to provide that information for you.
Btw, why do you only ask about which x86_32 devices use memory-failure,
but not which x86_32 devices use sparsemem? This patch just allows both
to coexist, and perhaps both are important?
Thanks!
Xie Yuanbin
next prev parent reply other threads:[~2025-11-05 2:45 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 [this message]
2025-11-05 8:12 ` David Hildenbrand (Red Hat)
2025-11-05 9:05 ` Xie Yuanbin
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=20251105024523.14300-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=david@redhat.com \
--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