From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
Muchun Song <muchun.song@linux.dev>,
Mina Almasry <almasrymina@google.com>, <kirill@shutemov.name>,
<joel@joelfernandes.org>, <william.kucharski@oracle.com>,
<kaleshsingh@google.com>, <linux-mm@kvack.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <21cnbao@gmail.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: [PATCH v2 0/2] mm: hugetlb: fix mremap tlb flush
Date: Tue, 1 Aug 2023 10:31:43 +0800 [thread overview]
Message-ID: <20230801023145.17026-1-wangkefeng.wang@huawei.com> (raw)
The first patch uses correct flush tlb functions when move page tables,
and second patch is a small tlb flush optimization for hugepage on arm64.
v2:
- drop uncorrected move_normal_pmd/pud() changes
- add flush_hugetlb_tlb_range() on arm64 instead of changing generic
flush_tlb_range()
- collect RB/ACK
Kefeng Wang (2):
mm: hugetlb: use flush_hugetlb_tlb_range() in
move_hugetlb_page_tables()
arm64: hugetlb: enable __HAVE_ARCH_FLUSH_HUGETLB_TLB_RANGE
arch/arm64/include/asm/hugetlb.h | 12 ++++++++++++
mm/hugetlb.c | 4 ++--
2 files changed, 14 insertions(+), 2 deletions(-)
--
2.41.0
next reply other threads:[~2023-08-01 2:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 2:31 Kefeng Wang [this message]
2023-08-01 2:31 ` [PATCH v2 1/2] mm: hugetlb: use flush_hugetlb_tlb_range() in move_hugetlb_page_tables() Kefeng Wang
2023-08-01 2:31 ` [PATCH v2 2/2] arm64: hugetlb: enable __HAVE_ARCH_FLUSH_HUGETLB_TLB_RANGE Kefeng Wang
2023-08-01 2:31 ` Muchun Song
2023-08-01 11:09 ` Catalin Marinas
2023-08-01 11:22 ` Kefeng Wang
2023-08-01 13:36 ` Kefeng Wang
2023-08-01 13:56 ` [PATCH v3] " Kefeng Wang
2023-08-01 15:28 ` Catalin Marinas
2023-08-02 1:27 ` [PATCH v4] " Kefeng Wang
2023-08-02 1:40 ` Muchun Song
2023-08-02 10:41 ` Catalin Marinas
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=20230801023145.17026-1-wangkefeng.wang@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=almasrymina@google.com \
--cc=catalin.marinas@arm.com \
--cc=joel@joelfernandes.org \
--cc=kaleshsingh@google.com \
--cc=kirill@shutemov.name \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=muchun.song@linux.dev \
--cc=will@kernel.org \
--cc=william.kucharski@oracle.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;
as well as URLs for NNTP newsgroup(s).