Re: [PATCH v3 5/5] mmu_notifiers: Rename invalidate_range notifier

2023-07-21 Thread Jason Gunthorpe
On Thu, Jul 20, 2023 at 06:39:27PM +1000, Alistair Popple wrote: > There are two main use cases for mmu notifiers. One is by KVM which > uses mmu_notifier_invalidate_range_start()/end() to manage a software > TLB. > > The other is to manage hardware TLBs which need to use the > invalidate_range()

Re: [PATCH v3 5/5] mmu_notifiers: Rename invalidate_range notifier

2023-07-21 Thread Catalin Marinas
On Thu, Jul 20, 2023 at 06:39:27PM +1000, Alistair Popple wrote: > diff --git a/arch/arm64/include/asm/tlbflush.h > b/arch/arm64/include/asm/tlbflush.h > index a99349d..84a05a0 100644 > --- a/arch/arm64/include/asm/tlbflush.h > +++ b/arch/arm64/include/asm/tlbflush.h > @@ -253,7 +253,7 @@ static i

[PATCH v3 5/5] mmu_notifiers: Rename invalidate_range notifier

2023-07-20 Thread Alistair Popple
There are two main use cases for mmu notifiers. One is by KVM which uses mmu_notifier_invalidate_range_start()/end() to manage a software TLB. The other is to manage hardware TLBs which need to use the invalidate_range() callback because HW can establish new TLB entries at any time. Hence using st