From: Nicholas Piggin <npiggin@gmail.com>
To: linux-mm@kvack.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
linuxppc-dev@lists.ozlabs.org, linux-arch@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/4] mm: mmu_gather changes to support explicit paging
Date: Thu, 26 Jul 2018 00:06:37 +1000 [thread overview]
Message-ID: <20180725140641.30372-1-npiggin@gmail.com> (raw)
The first 3 patches in this series are some generic mm changes I
would like to make, including a possible fix which may(?) be needed
for ARM64. Other than the bugfix, these first 3 patches should not
change anything so hopefully they aren't too controversial.
The powerpc patch is also there for reference.
Thanks,
Nick
Nicholas Piggin (4):
mm: move tlb_table_flush to tlb_flush_mmu_free
mm: mmu_notifier fix for tlb_end_vma
mm: allow arch to have tlb_flush caled on an empty TLB range
powerpc/64s/radix: optimise TLB flush with precise TLB ranges in
mmu_gather
arch/powerpc/include/asm/tlb.h | 34 +++++++++++++++++++++++++++++++++
arch/powerpc/mm/tlb-radix.c | 10 ++++++++++
include/asm-generic/tlb.h | 35 ++++++++++++++++++++++++++++++----
mm/memory.c | 14 ++------------
4 files changed, 77 insertions(+), 16 deletions(-)
--
2.17.0
next reply other threads:[~2018-07-25 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 14:06 Nicholas Piggin [this message]
2018-07-25 14:06 ` [RFC PATCH 1/4] mm: move tlb_table_flush to tlb_flush_mmu_free Nicholas Piggin
2018-07-25 14:06 ` [RFC PATCH 2/4] mm: mmu_notifier fix for tlb_end_vma Nicholas Piggin
2018-07-25 14:06 ` [RFC PATCH 3/4] mm: allow arch to have tlb_flush caled on an empty TLB range Nicholas Piggin
2018-07-25 14:06 ` [RFC PATCH 4/4] powerpc/64s/radix: optimise TLB flush with precise TLB ranges in mmu_gather Nicholas Piggin
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=20180725140641.30372-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).