On Mon, Nov 16, 2026 at 1:48 PM Arnd Bergmann <[email protected]> wrote:
> From: Arnd Bergmann <[email protected]> > > As Jason Gunthorpe noticed, supporting VIVT caches adds some complications > to highmem that can be avoided these days: > > While all ARMv4 and ARMv5 CPUs use virtually indexed caches, they no > longer really need highmem because we have practically discontinued > support for large-memory configurations already. The only machines I > could find anywhere for memory on ARMv5 are: > > - The Intel IOP platform was used on relatively large memory > configurations but we dropped kernel support in 2019 and 2022, > respectively. > > - The Marvell mv78xx0 platform was the initial user of Arm highmem, > with the DB-78x00-BP supporting 2GB of memory. The only remaining > board file is for Buffalo WLX (Terastation Duo), which has only > 512MB and is going to be removed soon. > > - The Kirkwood platform supports 2GB, and there are actually boards > with that configuration that can still work. However, there are > no known users of the OpenBlocks A7, and the Freebox V6 is already > using CONFIG_VMSPLIT_2G to avoid enabling highmem. > > Remove the Arm specific portions here, making CONFIG_HIGHMEM conditional > on modern caches. Since the cache type is enforced by Kconfig, no > boot time check is needed here. > > Link: https://lore.kernel.org/all/[email protected]/ > Suggested-by: Jason Gunthorpe <[email protected]> > Acked-by: Lorenzo Stoakes (ARM) <[email protected]> > Signed-off-by: Arnd Bergmann <[email protected]> Good riddance I'd say. I'd choose VMSPLIT_2G over highmem any day. Reviewed-by: Linus Walleij <[email protected]> Yours, Linus Walleij
