From: Xie Yuanbin <xieyuanbin1@huawei.com>
To: <arnd@arndb.de>
Cc: <Liam.Howlett@oracle.com>, <akpm@linux-foundation.org>,
<ardb@kernel.org>, <dave@vasilevsky.ca>, <david@redhat.com>,
<ebiggers@kernel.org>, <kees@kernel.org>, <liaohua4@huawei.com>,
<lilinjie8@huawei.com>, <linmiaohe@huawei.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<linux@armlinux.org.uk>, <lorenzo.stoakes@oracle.com>,
<mhocko@suse.com>, <nao.horiguchi@gmail.com>, <nathan@kernel.org>,
<peterz@infradead.org>, <rmk+kernel@armlinux.org.uk>,
<rostedt@goodmis.org>, <rppt@kernel.org>, <surenb@google.com>,
<vbabka@suse.cz>, <will@kernel.org>, <xieyuanbin1@huawei.com>
Subject: Re: [RFC PATCH 1/2] ARM: mm: support memory-failure
Date: Mon, 22 Sep 2025 16:28:43 +0800 [thread overview]
Message-ID: <20250922082843.26722-1-xieyuanbin1@huawei.com> (raw)
In-Reply-To: <727caa4f-5be5-4b59-a10e-8dc9bbc384bf@app.fastmail.com>
> It would be helpful to be more specific about what you
> want to do with this.
>
> Are you working on a driver that would actually make use of
> the exported interface?
Thanks for your reply.
Yes, In fact, we have developed a hardware component to detect DDR bit
transitions (software does not sense the detection behavior). Once a bit
transition is detected, an interrupt is reported to the CPU.
On the software side, we have developed a driver module ko to register
the interrupt callback to perform soft page offline to the corresponding
physical pages.
In fact, we will export `soft_offline_page` for ko to use (we can ensure
that it is not called in the interrupt context), but I have looked at the
code and found that `memory_failure_queue` and `memory_failure` can also
be used, which are already exported.
> I see only a very small number of
> drivers that call memory_failure(), and none of them are
> usable on Arm.
I think that not all drivers are in the open source kernel code.
As far as I know, there should be similar third-party drivers in other
architectures that use memory-failure functions, like x86 or arm64.
I am not a specialist in drivers, so if I have made any mistakes,
please correct me.
Xie Yuanbin
next prev parent reply other threads:[~2025-09-22 8:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 2:14 Xie Yuanbin
2025-09-22 2:14 ` [RFC PATCH 2/2] ARM: memory-failure: not select RAS and MEMORY_ISOLATION Xie Yuanbin
2025-09-22 8:15 ` David Hildenbrand
2025-09-22 8:47 ` [RFC PATCH 1/2] ARM: mm: support memory-failure Xie Yuanbin
2025-09-22 6:37 ` Arnd Bergmann
2025-09-22 8:28 ` Xie Yuanbin [this message]
2025-09-22 12:51 ` Arnd Bergmann
2025-09-23 4:10 ` Xie Yuanbin
2025-11-03 16:53 ` David Hildenbrand (Red Hat)
2025-11-04 13:48 ` Xie Yuanbin
2025-10-22 3:58 ` 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=20250922082843.26722-1-xieyuanbin1@huawei.com \
--to=xieyuanbin1@huawei.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=dave@vasilevsky.ca \
--cc=david@redhat.com \
--cc=ebiggers@kernel.org \
--cc=kees@kernel.org \
--cc=liaohua4@huawei.com \
--cc=lilinjie8@huawei.com \
--cc=linmiaohe@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@armlinux.org.uk \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=nao.horiguchi@gmail.com \
--cc=nathan@kernel.org \
--cc=peterz@infradead.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=will@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