Re: [PATCH] mm/Kconfig: allow user to select MIGRATION if MEMORY_FAILURE is enabled

[Miaohe Lin <linmiaohe@huawei.com>]

On 2026/8/13 17:32, Lorenzo Stoakes (ARM) wrote:
> On Thu, Aug 13, 2026 at 05:23:43PM +0800, Xie Yuanbin wrote:
>> Thanks for replying.
>>
>> On Thu, 13 Aug 2026 11:11:11 +0200, David Hildenbrand wrote:
>>> On 8/13/26 09:23, Xie Yuanbin wrote:
>>>> I think that just making MEMORY_FAILURE select MIGRATION is also a very
>>>> good solution, and I respect the maintainers' opinion.
>>>
>>> There must be a good reason to do something fine grained like
>>> MEMORY_FAILURE_MIGRATON, really.
>>>
>>> So if there is a use case out there that absolutely doesn't want
>>> CONFIG_MIGRATION but does want CONFIG_MEMORY_FAILURE, we could discuss it.
>>
>> At least so far, I haven't encountered such a use case.
>>
>>> As really only softdirty needs page migration (IIRC), we could also just put
>>> that under a separate config that implies CONFIG_MIGRATION, like
>>> CONFIG_MEMORY_FAILURE_SOFT_OFFLINE. But I'd rather avoid that unless really
>>> required.
>>
>> Okay, I understand it now. Making MEMORY_FAILURE select MIGRATION should
>> be enough.
> 
> Agreed with all that David says, and yes that seems the best way.

+1.

Thanks all.
.

> 
> 
> --
> Cheers, Lorenzo
> .
>