From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Xie Yuanbin <xieyuanbin1@huawei.com>,
akpm@linux-foundation.org, david@kernel.org,
linmiaohe@huawei.com, ziy@nvidia.com, matthew.brost@intel.com,
joshua.hahnjy@gmail.com, rakie.kim@sk.com, byungchul@sk.com,
ying.huang@linux.alibaba.com, apopple@nvidia.com,
nao.horiguchi@gmail.com, liam@infradead.org, vbabka@kernel.org,
surenb@google.com, mhocko@suse.com, gourry@gourry.net,
tony.luck@intel.com, bp@alien8.de, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, liaohua4@huawei.com,
lilinjie8@huawei.com
Subject: Re: [PATCH] mm/Kconfig: allow user to select MIGRATION if MEMORY_FAILURE is enabled
Date: Thu, 13 Aug 2026 10:25:55 +0100 [thread overview]
Message-ID: <an2NjwBTWoX7l_tH@lucifer> (raw)
In-Reply-To: <anx13IlH6PMxhaSL@kernel.org>
On Wed, Aug 12, 2026 at 04:32:12PM +0300, Mike Rapoport wrote:
> On Wed, Aug 12, 2026 at 11:55:03AM +0100, Lorenzo Stoakes (ARM) wrote:
> > On Wed, Aug 12, 2026 at 01:45:30PM +0300, Mike Rapoport wrote:
> > > Hi,
> > >
> > > On Wed, Aug 12, 2026 at 05:16:44PM +0800, Xie Yuanbin wrote:
> > > > Currently, memory-failure can be enabled without migration. However,
> > > > migration cannot be selected by user when memory-failure is enabled.
> > > >
> > > > Migration is very useful for soft_offline_page(), which may be triggered
> > > > by correctable memory errors. Most of the anonymous or file-mapping
> > > > faulty pages can be migrated to other healthy pages.
> > > >
> > > > Allow user to select MIGRATION if MEMORY_FAILURE is enabled.
> > > > Also, select MIGRATION by default if MEMORY_FAILURE is enabled.
> > >
> > > Do we want to make users decide if they need MIGRATION when MEMORY_FAILURE
> > > is enabled?
> > >
> > > Just make MEMORY_FAILURE select MIGRATION.
> >
> > NO.
> >
> > Explain first why the hell one of the other options that selection migration
> > can't be enabled.
>
> Think small systems ;-P
That need soft offline and migration?...
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-08-13 9:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 9:16 [PATCH] mm/Kconfig: allow user to select MIGRATION if MEMORY_FAILURE is enabled Xie Yuanbin
2026-08-12 10:45 ` Mike Rapoport
2026-08-12 10:55 ` Lorenzo Stoakes (ARM)
2026-08-12 13:32 ` Mike Rapoport
2026-08-13 9:25 ` Lorenzo Stoakes (ARM) [this message]
2026-08-13 9:31 ` Lorenzo Stoakes (ARM)
2026-08-13 2:26 ` Xie Yuanbin
2026-08-13 7:06 ` David Hildenbrand (Arm)
2026-08-13 7:23 ` Xie Yuanbin
2026-08-13 9:11 ` David Hildenbrand (Arm)
2026-08-13 9:23 ` Xie Yuanbin
2026-08-13 9:32 ` Lorenzo Stoakes (ARM)
2026-08-13 12:14 ` Miaohe Lin
2026-08-12 10:53 ` Lorenzo Stoakes (ARM)
2026-08-12 11:55 ` Xie Yuanbin
2026-08-13 9:31 ` Lorenzo Stoakes (ARM)
2026-08-12 10:58 ` 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=an2NjwBTWoX7l_tH@lucifer \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=bp@alien8.de \
--cc=byungchul@sk.com \
--cc=david@kernel.org \
--cc=gourry@gourry.net \
--cc=joshua.hahnjy@gmail.com \
--cc=liam@infradead.org \
--cc=liaohua4@huawei.com \
--cc=lilinjie8@huawei.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.brost@intel.com \
--cc=mhocko@suse.com \
--cc=nao.horiguchi@gmail.com \
--cc=rakie.kim@sk.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=tony.luck@intel.com \
--cc=vbabka@kernel.org \
--cc=xieyuanbin1@huawei.com \
--cc=ying.huang@linux.alibaba.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.