From: Jason Gunthorpe <jgg@ziepe•ca>
To: Alistair Popple <apopple@nvidia•com>
Cc: kevin.tian@intel•com, x86@kernel•org, ajd@linux•ibm.com,
kvm@vger•kernel.org, catalin.marinas@arm•com, seanjc@google•com,
will@kernel•org, linux-kernel@vger•kernel.org, npiggin@gmail•com,
zhi.wang.linux@gmail•com, linux-mm@kvack•org,
iommu@lists•linux.dev, sj@kernel•org, nicolinc@nvidia•com,
jhubbard@nvidia•com, fbarrat@linux•ibm.com,
akpm@linux-foundation•org, linuxppc-dev@lists•ozlabs.org,
linux-arm-kernel@lists•infradead.org, robin.murphy@arm•com
Subject: Re: [PATCH v3 4/5] mmu_notifiers: Don't invalidate secondary TLBs as part of mmu_notifier_invalidate_range_end()
Date: Fri, 21 Jul 2023 16:29:13 -0300 [thread overview]
Message-ID: <ZLrciTXW9CfLCLar@ziepe.ca> (raw)
In-Reply-To: <141e786b68527b1db9fc5a3259066c360448e7a4.1689842332.git-series.apopple@nvidia.com>
On Thu, Jul 20, 2023 at 06:39:26PM +1000, Alistair Popple wrote:
> Secondary TLBs are now invalidated from the architecture specific TLB
> invalidation functions. Therefore there is no need to explicitly
> notify or invalidate as part of the range end functions. This means we
> can remove mmu_notifier_invalidate_range_end_only() and some of the
> ptep_*_notify() functions.
>
> Signed-off-by: Alistair Popple <apopple@nvidia•com>
> ---
> include/linux/mmu_notifier.h | 56 +------------------------------------
> kernel/events/uprobes.c | 2 +-
> mm/huge_memory.c | 25 ++---------------
> mm/hugetlb.c | 1 +-
> mm/memory.c | 8 +----
> mm/migrate_device.c | 9 +-----
> mm/mmu_notifier.c | 25 ++---------------
> mm/rmap.c | 40 +--------------------------
> 8 files changed, 14 insertions(+), 152 deletions(-)
Reviewed-by: Jason Gunthorpe <jgg@nvidia•com>
Jason
next prev parent reply other threads:[~2023-07-21 19:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 8:39 [PATCH v3 0/5] Invalidate secondary IOMMU TLB on permission upgrade Alistair Popple
2023-07-20 8:39 ` [PATCH v3 1/5] arm64/smmu: Use TLBI ASID when invalidating entire range Alistair Popple
2023-07-21 19:25 ` Jason Gunthorpe
2023-07-20 8:39 ` [PATCH v3 2/5] mmu_notifiers: Fixup comment in mmu_interval_read_begin() Alistair Popple
2023-07-21 19:26 ` Jason Gunthorpe
2023-07-20 8:39 ` [PATCH v3 3/5] mmu_notifiers: Call invalidate_range() when invalidating TLBs Alistair Popple
2023-07-21 18:25 ` Catalin Marinas
2023-07-21 19:27 ` Jason Gunthorpe
2023-07-20 8:39 ` [PATCH v3 4/5] mmu_notifiers: Don't invalidate secondary TLBs as part of mmu_notifier_invalidate_range_end() Alistair Popple
2023-07-21 19:29 ` Jason Gunthorpe [this message]
2023-07-20 8:39 ` [PATCH v3 5/5] mmu_notifiers: Rename invalidate_range notifier Alistair Popple
2023-07-21 18:25 ` Catalin Marinas
2023-07-21 19:31 ` Jason Gunthorpe
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=ZLrciTXW9CfLCLar@ziepe.ca \
--to=jgg@ziepe$(echo .)ca \
--cc=ajd@linux$(echo .)ibm.com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=apopple@nvidia$(echo .)com \
--cc=catalin.marinas@arm$(echo .)com \
--cc=fbarrat@linux$(echo .)ibm.com \
--cc=iommu@lists$(echo .)linux.dev \
--cc=jhubbard@nvidia$(echo .)com \
--cc=kevin.tian@intel$(echo .)com \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=nicolinc@nvidia$(echo .)com \
--cc=npiggin@gmail$(echo .)com \
--cc=robin.murphy@arm$(echo .)com \
--cc=seanjc@google$(echo .)com \
--cc=sj@kernel$(echo .)org \
--cc=will@kernel$(echo .)org \
--cc=x86@kernel$(echo .)org \
--cc=zhi.wang.linux@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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