[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aHdIYXvppA6RKxic@kernel.org>
Date: Wed, 16 Jul 2025 09:36:17 +0300
From: Mike Rapoport <rppt@...nel.org>
To: Anthony Yznaga <anthony.yznaga@...cle.com>
Cc: davem@...emloft.net, andreas@...sler.com, arnd@...db.de,
muchun.song@...ux.dev, osalvador@...e.de, akpm@...ux-foundation.org,
david@...hat.com, lorenzo.stoakes@...cle.com,
Liam.Howlett@...cle.com, vbabka@...e.cz, surenb@...gle.com,
mhocko@...e.com, linux-mm@...ck.org, sparclinux@...r.kernel.org,
linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
alexghiti@...osinc.com, agordeev@...ux.ibm.com,
anshuman.khandual@....com, christophe.leroy@...roup.eu,
ryan.roberts@....com, will@...nel.org
Subject: Re: [PATCH 0/3] drop hugetlb_free_pgd_range()
On Tue, Jul 15, 2025 at 06:26:08PM -0700, Anthony Yznaga wrote:
> For all architectures that support hugetlb except for sparc,
> hugetlb_free_pgd_range() just calls free_pgd_range(). It turns out
> the sparc implementation is essentially identical to free_pgd_range()
> and can be removed. Remove it and update free_pgtables() to treat
> hugetlb VMAs the same as others.
>
> Anthony Yznaga (3):
> sparc64: remove hugetlb_free_pgd_range()
> mm: remove call to hugetlb_free_pgd_range()
> mm: drop hugetlb_free_pgd_range()
Acked-by: Mike Rapoport (Microsoft) <rppt@...nel.org>
> arch/sparc/include/asm/hugetlb.h | 5 --
> arch/sparc/mm/hugetlbpage.c | 119 -------------------------------
> include/asm-generic/hugetlb.h | 9 ---
> include/linux/hugetlb.h | 7 --
> mm/memory.c | 42 +++++------
> 5 files changed, 18 insertions(+), 164 deletions(-)
>
> --
> 2.47.1
>
--
Sincerely yours,
Mike.
Powered by blists - more mailing lists