Hi Arnd, On Thu, Jan 14, 2021 at 1:25 PM Arnd Bergmann <arnd@xxxxxxxxxx> wrote: > | arch/mips/Kconfig:config HIGHMEM > | arch/xtensa/Kconfig:config HIGHMEM > > AFAICT On MIPS (prior to MIPS32r3) and xtensa, you have at > most 512MB in the linear map, so the VMSPLIT_2G or VMSPLIT_4G_4G > tricks won't work. Regarding xtensa this was done to minimize difference between MMUv2 and MMUv3 virtual memory layouts. MMUv2 has been obsoleted more than 10 years ago, and MMUv3 is much more flexible and can do e.g. 4GB linear map. The only piece of xtensa MMUv2 hardware that I have has 96MB of DRAM which fits into its linear mapping. So maybe it's time to do a cleanup and rearrange virtual memory layout to eliminate the need of highmem. > I have no idea who uses xtensa systems with lots of memory on > modern kernels. We definitely use it for development internally at Cadence/Tensilica, mainly on simulators, but also on FPGA boards (e.g. on KC705 we can use all of the 1GB onboard DRAM). In the last few years we've had a few support requests for linux on xtensa cores with MMU, but AFAICT none of them had to deal with more than 512MB of onboard memory. -- Thanks. -- Max
