Re: [PATCH v3 07/13] mm/huge_memory: deduplicate zap deposited table call

Baolin Wang
2026-03-21T05:40:10Z

On 3/21/26 2:07 AM, Lorenzo Stoakes (Oracle) wrote:
> Rather than having separate logic for each case determining whether to zap
> the deposited table, simply track this via a boolean.
>
> We default this to whether the architecture requires it, and update it as
> required elsewhere.
>
> Signed-off-by: Lorenzo Stoakes (Oracle) <ljs@kernel.org>
> ---

Thanks. The logic is much clearer now.
Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>