[PATCH v5 7/8] mm/hugetlb: fix suboptimal migration/hwpoisoned entry check

Currently hugetlb_fault() checks at first whether pte of the faulted address is a migration or hwpoisoned entry, which means that we call huge_ptep_get() twice in single hugetlb_fault(). This is not optimized. The reason of this approach is that without checking at first, huge_pte_alloc() can

[PATCH v5 7/8] mm/hugetlb: fix suboptimal migration/hwpoisoned entry check

Currently hugetlb_fault() checks at first whether pte of the faulted address is a migration or hwpoisoned entry, which means that we call huge_ptep_get() twice in single hugetlb_fault(). This is not optimized. The reason of this approach is that without checking at first, huge_pte_alloc() can