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

From: Baolin Wang

Date: Sat Mar 21 2026 - 01:41:34 EST




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@xxxxxxxxxx>
---

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