Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Arnd Bergmann <arnd@kernel.org>, linux-mm@kvack.org
Cc: Arnd Bergmann <arnd@arndb.de>,
	Andreas Larsson <andreas@gaisler.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
	Jason Gunthorpe <jgg@nvidia.com>,
	Linus Walleij <linusw@kernel.org>,
	"Lorenzo Stoakes (ARM)" <ljs@kernel.org>,
	Lucas Stach <l.stach@pengutronix.de>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Malin Jonsson <malin.jonsson@est.tech>,
	Matthew Wilcox <willy@infradead.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Michal Simek <monstr@monstr.eu>, Mike Rapoport <rppt@kernel.org>,
	Nicholas Piggin <npiggin@gmail.com>, Nishanth Menon <nm@ti.com>,
	Richard Weinberger <richard@nod.at>,
	Russell King <linux@armlinux.org.uk>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-arm-kernel@lists.infradead.org,
	linux-fsdevel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	x86@kernel.org
Subject: Re: [PATCH v3 00/10] mm: highmem cleanups
Date: Tue, 17 Nov 2026 11:07:27 +0100	[thread overview]
Message-ID: <badc4186-b60b-46a9-ab75-ea85ee6965b8@kernel.org> (raw)
In-Reply-To: <20261116124832.662455-1-arnd@kernel.org>

On 11/16/26 13:48, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> 
> This is an updated series from what I posted last year [1] and
> last week[2].
> 
> At LPC 2025 [3], we got rough consensus on the plan to keep the
> funcationality present for the time being but instead reduce the scope
> of highmem in the kernel as much as we can without hurting users.
> 
> The short summary is a three stage process:
> 
>  1. Nudge users towards using a larger lowmem zone with the
>     CONFIG_VMSPLIT_* options if at all possible.
> 
>  2. Drop most __GFP_HIGHMEM allocations and corresponding kmap()
>     calls from the kernel, leaving only the subset that is likely
>     to contain the majority of the actual allocations.
>     Specifically we will keep anonymous and regular file backed
>     user mappings, zsmalloc, and huge pages.
> 
>  3. In a few years, also drop the page cache allocations and leave
>     perhaps only zsmalloc using a much simpler interface.  I suggested
>     five years as the time until we do this, but the timing depends a
>     lot on how the first two stages work out in practice, and how long
>     the remaining highmem users plan to keep updating their kernels.
> 
> This series implements stage 1, mostly using Kconfig changes to the
> default settings but leaving the traditional behavior as a CONFIG_EXPERT
> choice in Kconfig. With the new defaults, most installations that use
> highmem today with 1 GiB or 2 GiB of system RAM will see all of their
> RAM in the lowmem zone after upgrading their kernels. My estimate is
> that instead of 80% to 90% of maintained embedded 32-bit systems, this
> should cover over 98%.
> 
> As I don't actually have hardware in the category that still needs
> highmem, I tested this using a qemu-system for Armv7 and PPC6xx running a
> Debian userland with all combinations of VMSPLIT and HIGHMEM options. I
> ran some kernel builds on the Arm guest to ensure that the new options
> don't cause functional or performance regressions for regular workloads
> that don't exceed the virtual address space. I also ran some tests
> with Firefox and was positively surprised to see that this still works
> on the VMSPLIT_2G_OPT configuration without highmem, though it gets
> close to both the address space and lowmem size limits.
> 
> The change to use VMSPLIT_3G_OPT by default on Armv5 means that I could
> include a patch to no longer support highmem at all on VIVT caches,
> as suggested by Jason Gunthorpe. I also included the patch to drop
> HIGHPTE support now, as suggested by David Hildenbrand.
> 
> The patches from this series are available in [4] for testing.
> 
> Once there are no further concerns about the contents, I would
> suggest merging this through the asm-generic tree, as it touches
> mostly architecture specific code and that is not easily split
> from the core mm/* code. Merging everything through the mm
> tree would of course also work.
> 
>      Arnd
> 
> [1] https://lore.kernel.org/all/20251219161559.556737-1-arnd@kernel.org/  # v1
> [2] https://lore.kernel.org/all/20261112112528.1116405-1-arnd@kernel.org/ # v2
> [3] https://lwn.net/Articles/1051010/
> [4] https://git.kernel.org/pub/scm/linux/kernel/git/arnd/playground.git/log/?h=highmem-7.4
> 
> Changes since v2:
> 
>  - Add preparation patch for Arm PXA [sashiko-bot] 
>  - Add preparation patch for powerpc32/kvm [sashiko-bot]
>  - Fix Arm ARCH_MMAP_RND_BITS_MAX calculation [sashiko-bot]
>  - Simplification for pte_alloc_one() [Mike Rapoport]
>  - Drop stale references to highpte [David Hildenbrand]
>  - improve __print_bad_page_map_pgtable()
>  - Split out Arm changes for CONFIG_VMSPLIT_2G_OPT
> 
> Changes since v1:
>  - rebase to v7.4-rc
>  - add patch to drop highpte
> 
> Arnd Bergmann (10):
>   ARM: remove support for highmem on VIVT
>   ARM: drop CONFIG_HIGHPTE support
>   ARM: pxa: support arbitrary PAGE_OFFSET
>   powerpc: kvm: allow flexible PAGE_OFFSET
>   arch/*: increase lowmem size to avoid highmem use
>   ARM: add CONFIG_VMSPLIT_2G_OPT option
>   ARM: defconfig: turn off highmem in favor of CONFIG_VMSPLIT_2G_OPT
>   mm: remove ARCH_NEEDS_KMAP_HIGH_GET
>   mm: drop HIGHPTE support altogether
>   mm: print pte in __print_bad_page_map_pgtable()
> 
>  arch/arm/Kconfig                            |  27 +++---
>  arch/arm/configs/aspeed_g5_defconfig        |   3 +-
>  arch/arm/configs/gemini_defconfig           |   1 -
>  arch/arm/configs/lpae.config                |   1 +
>  arch/arm/configs/multi_v5_defconfig         |   1 -
>  arch/arm/configs/multi_v7_defconfig         |   1 +
>  arch/arm/configs/mvebu_v5_defconfig         |   1 -
>  arch/arm/configs/omap2plus_defconfig        |   1 +
>  arch/arm/configs/u8500_defconfig            |   1 -
>  arch/arm/configs/vt8500_v6_v7_defconfig     |   2 -
>  arch/arm/include/asm/highmem.h              |  56 +----------
>  arch/arm/include/asm/pgalloc.h              |  13 +--
>  arch/arm/mach-omap2/Kconfig                 |   1 -
>  arch/arm/mach-pxa/pxa3xx.c                  |   2 +-
>  arch/arm/mm/cache-feroceon-l2.c             |  31 +-----
>  arch/arm/mm/cache-xsc3l2.c                  |  47 +--------
>  arch/arm/mm/dma-mapping.c                   |  12 +--
>  arch/arm/mm/flush.c                         |  19 +---
>  arch/microblaze/Kconfig                     |   9 +-
>  arch/microblaze/configs/mmu_defconfig       |   1 -
>  arch/powerpc/Kconfig                        |  24 +++--
>  arch/powerpc/configs/44x/akebono_defconfig  |   1 -
>  arch/powerpc/configs/85xx/ksi8560_defconfig |   1 -
>  arch/powerpc/configs/85xx/stx_gp3_defconfig |   1 -
>  arch/powerpc/kvm/book3s_32_sr.S             |   4 +-
>  arch/powerpc/kvm/booke_interrupts.S         |   4 +-
>  arch/powerpc/kvm/e500_mmu_host.c            |   3 +-
>  arch/x86/Kconfig                            |   4 +-
>  include/linux/hugetlb.h                     |   5 +-
>  include/linux/mm.h                          |   1 -
>  include/linux/pgtable.h                     |  13 ---
>  mm/highmem.c                                | 100 ++------------------
>  mm/memory.c                                 |  21 ++--
>  mm/pgtable-generic.c                        |  25 +++--
>  mm/userfaultfd.c                            |   6 +-

I can pick up the MM patches after the ARM stuff upstream, or the MM patches can
go upstream in the same go as the ARM stuff.

I don't expect conflicts in that area.

Just let me know what you+people prefer.

-- 
Cheers,

David


      parent reply	other threads:[~2026-11-17 10:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 12:48 [PATCH v3 00/10] mm: highmem cleanups Arnd Bergmann
2026-11-16 12:48 ` [PATCH v3 01/10] ARM: remove support for highmem on VIVT Arnd Bergmann
2026-11-16 12:48 ` [PATCH v3 02/10] ARM: drop CONFIG_HIGHPTE support Arnd Bergmann
2026-11-16 12:48 ` [PATCH v3 03/10] ARM: pxa: support arbitrary PAGE_OFFSET Arnd Bergmann
2026-11-16 12:48 ` [PATCH v3 04/10] powerpc: kvm: allow flexible PAGE_OFFSET Arnd Bergmann
2026-11-16 13:38   ` Christophe Leroy (CS GROUP)
2026-11-16 22:54     ` Arnd Bergmann
2026-11-16 12:48 ` [PATCH v3 05/10] ARM: add CONFIG_VMSPLIT_2G_OPT option Arnd Bergmann
2026-11-16 12:48 ` [PATCH v3 06/10] arch/*: increase lowmem size to avoid highmem use Arnd Bergmann
2026-11-16 12:48 ` [PATCH v3 07/10] ARM: defconfig: turn off highmem in favor of CONFIG_VMSPLIT_2G_OPT Arnd Bergmann
2026-11-16 12:48 ` [PATCH v3 08/10] mm: remove ARCH_NEEDS_KMAP_HIGH_GET Arnd Bergmann
2026-11-17 10:05   ` David Hildenbrand (Arm)
2026-11-16 12:48 ` [PATCH v3 09/10] mm: drop HIGHPTE support altogether Arnd Bergmann
2026-11-16 12:48 ` [PATCH v3 10/10] mm: print pte in __print_bad_page_map_pgtable() Arnd Bergmann
2026-11-16 13:00   ` Mike Rapoport
2026-11-17 10:07 ` David Hildenbrand (Arm) [this message]

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=badc4186-b60b-46a9-ab75-ea85ee6965b8@kernel.org \
    --to=david@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=andreas@gaisler.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=chleroy@kernel.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jgg@nvidia.com \
    --cc=l.stach@pengutronix.de \
    --cc=linusw@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@armlinux.org.uk \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=ljs@kernel.org \
    --cc=maddy@linux.ibm.com \
    --cc=malin.jonsson@est.tech \
    --cc=mingo@redhat.com \
    --cc=monstr@monstr.eu \
    --cc=mpe@ellerman.id.au \
    --cc=nm@ti.com \
    --cc=npiggin@gmail.com \
    --cc=richard@nod.at \
    --cc=rppt@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=willy@infradead.org \
    --cc=x86@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