From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Steve Capper <steve.capper@arm.com>, linux-mm@kvack.org
Cc: David Hildenbrand <david@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH v2] tlb: hugetlb: Add more sizes to tlb_remove_huge_tlb_entry
Date: Wed, 30 Mar 2022 19:34:16 +0530 [thread overview]
Message-ID: <cd075502-0c44-2c38-90fd-869966651d50@arm.com> (raw)
In-Reply-To: <20220330112543.863-1-steve.capper@arm.com>
On 3/30/22 16:55, Steve Capper wrote:
> tlb_remove_huge_tlb_entry only considers PMD_SIZE and PUD_SIZE when
> updating the mmu_gather structure.
>
> Unfortunately on arm64 there are two additional huge page sizes that
> need to be covered: CONT_PTE_SIZE and CONT_PMD_SIZE. Where an end-user
> attempts to employ contiguous huge pages, a VM_BUG_ON can be experienced
> due to the fact that the tlb structure hasn't been correctly updated by
> the relevant tlb_flush_p.._range() call from tlb_remove_huge_tlb_entry.
>
> This patch adds inequality logic to the generic implementation of
> tlb_remove_huge_tlb_entry s.t. CONT_PTE_SIZE and CONT_PMD_SIZE are
> effectively covered on arm64. Also, as well as ptes, pmds and puds;
> p4ds are now considered too.
>
> Reported-by: David Hildenbrand <david@redhat.com>
> Suggested-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> Cc: Anshuman Khandual <anshuman.khandual@arm.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Link: https://lore.kernel.org/linux-mm/811c5c8e-b3a2-85d2-049c-717f17c3a03a@redhat.com/
> Signed-off-by: Steve Capper <steve.capper@arm.com>
>
> ---
>
> Changed in V2: instead of doing the per-arch implementation of
> tlb_remove_huge_tlb_entry we add to the generic implmentation, as
> suggested by PeterZ.
>
> This works well on arm64 with contiguous PTEs/PMDs. Does this look
> reasonable to the ppc folk?
I am wondering whether this should take care of gigantic PGDIR_SIZE
based HugeTLB pages as well ? Although, it will require another new
helper tlb_flush_pgd_range(). Any thoughts ?
>
> Cheers,
> --
> Steve
> ---
> include/asm-generic/tlb.h | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/include/asm-generic/tlb.h b/include/asm-generic/tlb.h
> index 2c68a545ffa7..71942a1c642d 100644
> --- a/include/asm-generic/tlb.h
> +++ b/include/asm-generic/tlb.h
> @@ -565,10 +565,14 @@ static inline void tlb_flush_p4d_range(struct mmu_gather *tlb,
> #define tlb_remove_huge_tlb_entry(h, tlb, ptep, address) \
> do { \
> unsigned long _sz = huge_page_size(h); \
> - if (_sz == PMD_SIZE) \
> - tlb_flush_pmd_range(tlb, address, _sz); \
> - else if (_sz == PUD_SIZE) \
> + if (_sz >= P4D_SIZE) \
> + tlb_flush_p4d_range(tlb, address, _sz); \
> + else if (_sz >= PUD_SIZE) \
> tlb_flush_pud_range(tlb, address, _sz); \
> + else if (_sz >= PMD_SIZE) \
> + tlb_flush_pmd_range(tlb, address, _sz); \
> + else \
> + tlb_flush_pte_range(tlb, address, _sz); \
> __tlb_remove_tlb_entry(tlb, ptep, address); \
> } while (0)
>
next prev parent reply other threads:[~2022-03-30 14:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 16:52 [PATCH] tlb: hugetlb: Add arm64 contiguous hint awareness Steve Capper
2022-03-23 18:30 ` Catalin Marinas
2022-03-24 14:33 ` Peter Zijlstra
2022-03-24 14:35 ` Steve Capper
2022-03-24 15:58 ` Peter Zijlstra
2022-03-24 16:11 ` Steve Capper
2022-03-30 11:25 ` [PATCH v2] tlb: hugetlb: Add more sizes to tlb_remove_huge_tlb_entry Steve Capper
2022-03-30 12:05 ` David Hildenbrand
2022-03-30 14:04 ` Anshuman Khandual [this message]
2022-04-06 11:21 ` Peter Zijlstra
2022-04-04 6:07 ` Anshuman Khandual
2022-04-05 14:26 ` Catalin Marinas
2022-04-06 11:40 ` Peter Zijlstra
2022-04-06 12:05 ` Will Deacon
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=cd075502-0c44-2c38-90fd-869966651d50@arm.com \
--to=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=steve.capper@arm.com \
--cc=will@kernel.org \
/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