From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Dev Jain <dev.jain@arm.com>, <akpm@linux-foundation.org>,
<david@redhat.com>, <willy@infradead.org>,
<kirill.shutemov@linux.intel.com>
Cc: <ryan.roberts@arm.com>, <anshuman.khandual@arm.com>,
<catalin.marinas@arm.com>, <cl@gentwo.org>, <vbabka@suse.cz>,
<mhocko@suse.com>, <apopple@nvidia.com>,
<dave.hansen@linux.intel.com>, <will@kernel.org>,
<baohua@kernel.org>, <jack@suse.cz>, <mark.rutland@arm.com>,
<hughd@google.com>, <aneesh.kumar@kernel.org>,
<yang@os.amperecomputing.com>, <peterx@redhat.com>,
<ioworker0@gmail.com>, <jglisse@google.com>, <ziy@nvidia.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: [PATCH v5 2/2] mm: Allocate THP on hugezeropage wp-fault
Date: Tue, 24 Sep 2024 21:13:20 +0800 [thread overview]
Message-ID: <7d21314c-9c53-4aa0-9a27-b07d21da429e@huawei.com> (raw)
In-Reply-To: <20240924101654.1777697-3-dev.jain@arm.com>
On 2024/9/24 18:16, Dev Jain wrote:
> Introduce do_huge_zero_wp_pmd() to handle wp-fault on a hugezeropage and
> replace it with a PMD-mapped THP. Remember to flush TLB entry
> corresponding to the hugezeropage. In case of failure, fallback
> to splitting the PMD.
>
> Signed-off-by: Dev Jain <dev.jain@arm.com>
> ---
> mm/huge_memory.c | 44 +++++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 43 insertions(+), 1 deletion(-)
>
> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> index bdbf67c18f6c..fbb195bc2038 100644
> --- a/mm/huge_memory.c
> +++ b/mm/huge_memory.c
> @@ -1790,6 +1790,41 @@ void huge_pmd_set_accessed(struct vm_fault *vmf)
> spin_unlock(vmf->ptl);
> }
>
> +static vm_fault_t do_huge_zero_wp_pmd(struct vm_fault *vmf)
> +{
> + unsigned long haddr = vmf->address & HPAGE_PMD_MASK;
> + struct vm_area_struct *vma = vmf->vma;
> + struct mmu_notifier_range range;
> + struct folio *folio;
> + vm_fault_t ret = 0;
> +
> + folio = vma_alloc_anon_folio_pmd(vma, vmf->address);
> + if (unlikely(!folio)) {
> + ret = VM_FAULT_FALLBACK;
I'd like to return VM_FAULT_FALLBACK if you re-post.
Reviewed-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> + goto out;
> + }
> +
> + mmu_notifier_range_init(&range, MMU_NOTIFY_CLEAR, 0, vma->vm_mm, haddr,
> + haddr + HPAGE_PMD_SIZE);
> + mmu_notifier_invalidate_range_start(&range);
> + vmf->ptl = pmd_lock(vma->vm_mm, vmf->pmd);
> + if (unlikely(!pmd_same(pmdp_get(vmf->pmd), vmf->orig_pmd)))
> + goto release;
> + ret = check_stable_address_space(vma->vm_mm);
> + if (ret)
> + goto release;
> + (void)pmdp_huge_clear_flush(vma, haddr, vmf->pmd);
> + map_anon_folio_pmd(folio, vmf->pmd, vma, haddr);
> + goto unlock;
> +release:
> + folio_put(folio);
> +unlock:
> + spin_unlock(vmf->ptl);
> + mmu_notifier_invalidate_range_end(&range);
> +out:
> + return ret;
> +}
> +
> vm_fault_t do_huge_pmd_wp_page(struct vm_fault *vmf)
> {
> const bool unshare = vmf->flags & FAULT_FLAG_UNSHARE;
> @@ -1802,8 +1837,15 @@ vm_fault_t do_huge_pmd_wp_page(struct vm_fault *vmf)
> vmf->ptl = pmd_lockptr(vma->vm_mm, vmf->pmd);
> VM_BUG_ON_VMA(!vma->anon_vma, vma);
>
> - if (is_huge_zero_pmd(orig_pmd))
> + if (is_huge_zero_pmd(orig_pmd)) {
> + vm_fault_t ret = do_huge_zero_wp_pmd(vmf);
> +
> + if (!(ret & VM_FAULT_FALLBACK))
> + return ret;
> +
> + /* Fallback to splitting PMD if THP cannot be allocated */
> goto fallback;
> + }
>
> spin_lock(vmf->ptl);
>
next prev parent reply other threads:[~2024-09-24 13:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 10:16 [PATCH v5 0/2] Do not shatter hugezeropage on wp-fault Dev Jain
2024-09-24 10:16 ` [PATCH v5 1/2] mm: Abstract THP allocation Dev Jain
2024-09-24 11:20 ` Kefeng Wang
2024-09-24 12:17 ` Dev Jain
2024-09-24 12:54 ` Kefeng Wang
2024-09-25 5:28 ` Dev Jain
2024-09-24 10:16 ` [PATCH v5 2/2] mm: Allocate THP on hugezeropage wp-fault Dev Jain
2024-09-24 12:20 ` David Hildenbrand
2024-09-24 13:13 ` Kefeng Wang [this message]
2024-09-25 5:31 ` Dev Jain
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=7d21314c-9c53-4aa0-9a27-b07d21da429e@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=apopple@nvidia.com \
--cc=baohua@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cl@gentwo.org \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=hughd@google.com \
--cc=ioworker0@gmail.com \
--cc=jack@suse.cz \
--cc=jglisse@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=mhocko@suse.com \
--cc=peterx@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=vbabka@suse.cz \
--cc=will@kernel.org \
--cc=willy@infradead.org \
--cc=yang@os.amperecomputing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®