From: Oscar Salvador <osalvador@suse.de>
To: Anthony Yznaga <anthony.yznaga@oracle.com>
Cc: davem@davemloft.net, andreas@gaisler.com, arnd@arndb.de,
muchun.song@linux.dev, akpm@linux-foundation.org,
david@redhat.com, lorenzo.stoakes@oracle.com,
Liam.Howlett@oracle.com, vbabka@suse.cz, rppt@kernel.org,
surenb@google.com, mhocko@suse.com, linux-mm@kvack.org,
sparclinux@vger.kernel.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, alexghiti@rivosinc.com,
agordeev@linux.ibm.com, anshuman.khandual@arm.com,
christophe.leroy@csgroup.eu, ryan.roberts@arm.com,
will@kernel.org
Subject: Re: [PATCH 0/3] drop hugetlb_free_pgd_range()
Date: Wed, 16 Jul 2025 10:05:53 +0200 [thread overview]
Message-ID: <aHddYU8elWhddpoP@localhost.localdomain> (raw)
In-Reply-To: <20250716012611.10369-1-anthony.yznaga@oracle.com>
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: Oscar Salvador <osalvador@sude.de>
Thanks!
--
Oscar Salvador
SUSE Labs
next prev parent reply other threads:[~2025-07-16 8:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 1:26 [PATCH 0/3] drop hugetlb_free_pgd_range() Anthony Yznaga
2025-07-16 1:26 ` [PATCH 1/3] sparc64: remove hugetlb_free_pgd_range() Anthony Yznaga
2025-07-16 8:20 ` David Hildenbrand
2025-07-16 16:42 ` Anthony Yznaga
2025-07-16 1:26 ` [PATCH 2/3] mm: remove call to hugetlb_free_pgd_range() Anthony Yznaga
2025-07-16 1:26 ` [PATCH 3/3] mm: drop hugetlb_free_pgd_range() Anthony Yznaga
2025-07-16 6:36 ` [PATCH 0/3] " Mike Rapoport
2025-07-16 8:05 ` Oscar Salvador [this message]
2025-07-16 8:16 ` Oscar Salvador
2025-07-25 7:50 ` John Paul Adrian Glaubitz
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=aHddYU8elWhddpoP@localhost.localdomain \
--to=osalvador@suse.de \
--cc=Liam.Howlett@oracle.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=alexghiti@rivosinc.com \
--cc=andreas@gaisler.com \
--cc=anshuman.khandual@arm.com \
--cc=anthony.yznaga@oracle.com \
--cc=arnd@arndb.de \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=david@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=sparclinux@vger.kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).