[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1206e86e-488c-4c58-9e67-2313a678a5a0@gmail.com>
Date: Wed, 10 Sep 2025 23:56:11 +0200
From: René Herman <rene.herman@...il.com>
To: richard@....at
Cc: Liam.Howlett@...cle.com, akpm@...ux-foundation.org,
alexander.sverdlin@...il.com, andreas@...sler.com, ankur.a.arora@...cle.com,
arnd@...db.de, chester.a.unal@...nc9.com, christophe.leroy@...roup.eu,
dave@...1.net, david@...hat.com, geert+renesas@...der.be, heiko@...ech.de,
imx@...ts.linux.dev, ira.weiny@...el.com, ksummit@...ts.linux.dev,
l.stach@...gutronix.de, linus.walleij@...aro.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mips@...r.kernel.org, linux-mm@...ck.org,
linuxppc-dev@...ts.ozlabs.org, lorenzo.stoakes@...cle.com, nm@...com,
rppt@...nel.org, sergio.paracuellos@...il.com, surenb@...gle.com,
vbabka@...e.cz, willy@...radead.org
Subject: Re: [TECH TOPIC] Reaching consensus on CONFIG_HIGHMEM phaseout
> In the past I saw that programs such as the Java Runtime (JRE) ran
> into address space limitations due to a 2G/2G split on embedded
> systems. Reverting to a 3G/1G split fixed the problems.
Believe you guys are talking specifically ARM so FWIW, but I remember
for x86 that at least initially Wine and things such as VMware were
affected by the more creative PAGE_OFFSET choices.
Both will have been as a matter of plain bugs and are supposedly long
fixed (and I in fact believe I recall such fixing for VMware). Never had
or as far as I recall heard of other issues back then.
Rene.
Powered by blists - more mailing lists