From: rob@landley.net (Rob Landley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: document the bigger pagetables needed for LPAE
Date: Sat, 25 May 2013 19:27:52 -0500 [thread overview]
Message-ID: <1369528072.2776.26@driftwood> (raw)
In-Reply-To: <1369410236-22398-1-git-send-email-javi.merino@arm.com> (from javi.merino@arm.com on Fri May 24 10:43:56 2013)
On 05/24/2013 10:43:56 AM, Javi Merino wrote:
> The Booting documentation assumes that the initial pagetables are
> 16KiB but since 1b6ba46 (ARM: LPAE: MMU setup for the 3-level page
> table format) they are 20KiB for LPAE kernels. Thus, the
> recommendation to put atags or the dtb in the first 16KiB is wrong,
> there's only 12KiB of space there in LPAE kernels, so update the
> documentation accordingly.
> ---
> Documentation/arm/Booting | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
Acked-by: Rob Landley <rob@landley.net>
With one comment:
> diff --git a/Documentation/arm/Booting b/Documentation/arm/Booting
> index 0c1f475..f6f9cd8 100644
> --- a/Documentation/arm/Booting
> +++ b/Documentation/arm/Booting
> @@ -105,7 +105,7 @@ The tagged list should be stored in system RAM.
>
> The tagged list must be placed in a region of memory where neither
> the kernel decompressor nor initrd 'bootp' program will overwrite
> -it. The recommended placement is in the first 16KiB of RAM.
> +it. The recommended placement is in the first 12KiB of RAM.
>
> 4b. Setup the device tree
> -------------------------
> @@ -120,7 +120,7 @@ tagged list.
> The boot loader must pass at a minimum the size and location of the
> system memory, and the root filesystem location. The dtb must be
> placed in a region of memory where the kernel decompressor will not
> -overwrite it. The recommended placement is in the first 16KiB of RAM
> +overwrite it. The recommended placement is in the first 12KiB of RAM
> with the caveat that it may not be located at physical address 0
> since
> the kernel interprets a value of 0 in r2 to mean neither a tagged
> list
> nor a dtb were passed.
> @@ -137,8 +137,9 @@ then it is legal for the boot loader to call the
> zImage in flash
> directly.
>
> The zImage may also be placed in system RAM (at any location) and
> -called there. Note that the kernel uses 16K of RAM below the image
> -to store page tables. The recommended placement is 32KiB into RAM.
> +called there. Note that the kernel may use up to 20KiB of RAM below
> +the image to store page tables. The recommended placement is 32KiB
> +into RAM.
Now that we have three memory entires, possibly some sort of memory
layout would be in order?
0k-12k boot data (tagged list or device tree)
12k-32k page tables
32k-xxx kernel image
Perhaps at the end of section 4's introduction? It's not quite obvious
from the document...
Rob
next prev parent reply other threads:[~2013-05-26 0:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 15:43 [PATCH] ARM: document the bigger pagetables needed for LPAE Javi Merino
2013-05-24 16:21 ` Catalin Marinas
2013-05-26 0:27 ` Rob Landley [this message]
2013-05-28 10:49 ` Javi Merino
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=1369528072.2776.26@driftwood \
--to=rob@landley.net \
--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