From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] WIP: HACK: LPAE, BOOTMEM and NO_BOOTMEM
Date: Sat, 29 Jun 2013 18:21:24 +0100 [thread overview]
Message-ID: <20130629172123.GA3353@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130629152959.GB31339@mtj.dyndns.org>
On Sat, Jun 29, 2013 at 08:29:59AM -0700, Tejun Heo wrote:
> I suppose LPAE on arm is analogous to PAE on x86, IOW, high memory?
> This does affect memory initilization as you need to register memory
> areas which aren't addressable directly; however, why does it affect
> generic code which is just allocating memory? Note that x86 already
> does highmem and the existing code works fine. Once all bootmem users
> are gone, we can remove the bootmem wrappers but I don't what the
> point is with introducing yet another wrapper.
The reason is actually quite simple: on x86 you always have memory
starting at physical address zero.
Unfortunately, that has not been true on ARM - it's very common for
there to be an offset on physical memory, sometimes of the order of
3GB or more. This is because on reset, ARMs start executing the code
at physical address zero, which therefore can't be RAM - and there's
a desire to avoid complex switching games in hardware to temporarily
map ROM there instead of RAM.
On these SoCs which Santosh is working on, the main physical memory
mapping is above 4GB, with just a small alias below 4GB to allow the
system to boot without the MMU being on, as they may have more than
4GB of RAM. As I understand it, the small alias below 4GB is not
suitable for use as a "lowmem" mapping.
next prev parent reply other threads:[~2013-06-29 17:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 1:01 [PATCH] WIP: HACK: LPAE, BOOTMEM and NO_BOOTMEM Santosh Shilimkar
2013-06-29 15:29 ` Tejun Heo
2013-06-29 17:21 ` Russell King - ARM Linux [this message]
2013-06-29 17:57 ` Tejun Heo
2013-06-29 18:23 ` H. Peter Anvin
2013-06-29 19:29 ` Yinghai Lu
2013-06-29 19:55 ` Russell King - ARM Linux
2013-06-29 20:08 ` Yinghai Lu
2013-07-01 14:10 ` Santosh Shilimkar
2013-07-25 22:33 ` Santosh Shilimkar
2013-07-25 22:36 ` Tejun Heo
2013-07-25 23:15 ` Santosh Shilimkar
2013-07-26 3:08 ` Tejun Heo
2013-08-02 21:06 ` Santosh Shilimkar
2013-08-05 15:01 ` Tejun Heo
2013-08-05 15:29 ` Santosh Shilimkar
2013-08-05 15:38 ` Tejun Heo
2013-08-05 15:47 ` Santosh Shilimkar
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=20130629172123.GA3353@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).