[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4650b888-d90f-40e3-8c53-c9949e539959@redhat.com>
Date: Tue, 21 May 2024 11:36:42 +0200
From: David Hildenbrand <david@...hat.com>
To: Bang Li <libang.li@...group.com>, akpm@...ux-foundation.org,
chenhuacai@...nel.org, tsbogend@...ha.franken.de, paul.walmsley@...ive.com,
palmer@...belt.com, chris@...kel.net, jcmvbkbc@...il.com
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
loongarch@...ts.linux.dev, linux-riscv@...ts.infradead.org,
ryan.roberts@....com, ioworker0@...il.com, libang.linux@...il.com
Subject: Re: [PATCH v3 2/3] mm: Refactor update_mmu_tlb()
On 18.05.24 09:49, Bang Li wrote:
> Remove update_mmu_tlb() from those architectures and define
> generically via update_mmu_tlb_range(), removing the ability
> for arches to override it.
I'd suggest something like
"mm: implement update_mmu_tlb() using update_mmu_tlb_range()
Let's make update_mmu_tlb() simply a generic wrapper around
update_mmu_tlb_range(). Only the latter can now be overridden by the
architecture. We can now remove __HAVE_ARCH_UPDATE_MMU_TLB as well.
"
[...]
> +#ifndef update_mmu_tlb_range
> +static inline void update_mmu_tlb_range(struct vm_area_struct *vma,
> + unsigned long address, pte_t *ptep, unsigned int nr)
> +{
> +}
> +#endif
With that in patch #1
Acked-by: David Hildenbrand <david@...hat.com>
--
Cheers,
David / dhildenb
Powered by blists - more mailing lists