Re: [PATCH v2 3/5] mmu_notifiers: Call invalidate_range() when invalidating TLBs

Michael Ellerman writes: > Alistair Popple writes: >> The invalidate_range() is going to become an architecture specific mmu >> notifier used to keep the TLB of secondary MMUs such as an IOMMU in >> sync with the CPU page tables. Currently it is called from separate >> code paths to the main C

Re: [PATCH v2 3/5] mmu_notifiers: Call invalidate_range() when invalidating TLBs

Alistair Popple writes: > The invalidate_range() is going to become an architecture specific mmu > notifier used to keep the TLB of secondary MMUs such as an IOMMU in > sync with the CPU page tables. Currently it is called from separate > code paths to the main CPU TLB invalidations. This can lead

Re: [PATCH v2 3/5] mmu_notifiers: Call invalidate_range() when invalidating TLBs

Luis Chamberlain writes: >> diff --git a/arch/x86/include/asm/tlbflush.h >> b/arch/x86/include/asm/tlbflush.h >> index 837e4a50281a..79c46da919b9 100644 >> --- a/arch/x86/include/asm/tlbflush.h >> +++ b/arch/x86/include/asm/tlbflush.h >> @@ -4,6 +4,7 @@ >> >> #include >> #include >> +#in

Re: [PATCH v2 3/5] mmu_notifiers: Call invalidate_range() when invalidating TLBs

Cc'ing fsdevel + xfs folks as this fixes a regression tests with XFS with generic/176. On Thu, Jul 20, 2023 at 10:52:59AM +1000, Alistair Popple wrote: > > SeongJae Park writes: > > > Hi Alistair, > > > > On Wed, 19 Jul 2023 22:18:44 +1000 Alistair Popple > > wrote: > > > >> The invalidate_ra

Re: [PATCH v2 3/5] mmu_notifiers: Call invalidate_range() when invalidating TLBs

On Thu, 20 Jul 2023 10:52:59 +1000 Alistair Popple wrote: > > SeongJae Park writes: > > > Hi Alistair, > > > > On Wed, 19 Jul 2023 22:18:44 +1000 Alistair Popple > > wrote: > > > >> The invalidate_range() is going to become an architecture specific mmu > >> notifier used to keep the TLB of s

Re: [PATCH v2 3/5] mmu_notifiers: Call invalidate_range() when invalidating TLBs

SeongJae Park writes: > Hi Alistair, > > On Wed, 19 Jul 2023 22:18:44 +1000 Alistair Popple wrote: > >> The invalidate_range() is going to become an architecture specific mmu >> notifier used to keep the TLB of secondary MMUs such as an IOMMU in >> sync with the CPU page tables. Currently it i

[PATCH v2 3/5] mmu_notifiers: Call invalidate_range() when invalidating TLBs

The invalidate_range() is going to become an architecture specific mmu notifier used to keep the TLB of secondary MMUs such as an IOMMU in sync with the CPU page tables. Currently it is called from separate code paths to the main CPU TLB invalidations. This can lead to a secondary TLB not getting i