From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] arm64: booti: allow to place kernel image anywhere in physical memory
Date: Wed, 22 Feb 2017 11:19:21 -0500 [thread overview]
Message-ID: <20170222161921.GS27120@bill-the-cat> (raw)
In-Reply-To: <1487730866-19447-2-git-send-email-yamada.masahiro@socionext.com>
On Wed, Feb 22, 2017 at 11:34:26AM +0900, Masahiro Yamada wrote:
> At first, the ARM64 Linux booting requirement recommended that the
> kernel image be placed text_offset bytes from 2MB aligned base near
> the start of usable system RAM because memory below that base address
> was unusable at that time.
>
> This requirement was relaxed by Linux commit a7f8de168ace ("arm64:
> allow kernel Image to be loaded anywhere in physical memory").
> Since then, the bit 3 of the flags field indicates the tolerance
> of the kernel physical placement. If this bit is set, the 2MB
> aligned base may be anywhere in physical memory. For details, see
> Documentation/arm64/booting.txt of Linux.
>
> The booti command should be also relaxed to not expect the kernel
> image at the start of the system RAM. Even when booting older
> kernel versions, it still makes sense to have some space below the
> kernel. For example, some firmware may sit at the start of the
> system RAM.
>
> After all, the most flexible way for booting the kernel is to respect
> the original images->ep instead of gd->bd->bi_dram[0].start. If
> image->ep (which is the address given to the booti command) already
> meets the address requirement, just use it. If not, relocate the
> kernel to the next 2MB aligned address.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>
> cmd/booti.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/cmd/booti.c b/cmd/booti.c
> index f65f0e7..9408c34 100644
> --- a/cmd/booti.c
> +++ b/cmd/booti.c
> @@ -11,6 +11,8 @@
> #include <image.h>
> #include <lmb.h>
> #include <mapmem.h>
> +#include <linux/kernel.h>
> +#include <linux/sizes.h>
>
> DECLARE_GLOBAL_DATA_PTR;
>
> @@ -54,7 +56,9 @@ static int booti_setup(bootm_headers_t *images)
> * If we are not at the correct run-time location, set the new
> * correct location and then move the image there.
> */
> - dst = gd->bd->bi_dram[0].start + le64_to_cpu(ih->text_offset);
> + dst = images->ep - ih->text_offset;
> + dst = ALIGN(dst, SZ_2M);
> + dst += ih->text_offset;
I think the code will be slightly more complex here but I would rather
see us check for the presence of the flag which allows for us to
relocate things rather than assume that we can always use the address
provided, or round it up. The 'contract' wwith the kernel previously
said it must be from start of memory and I'd rather not change that.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170222/16ba6164/attachment.sig>
next prev parent reply other threads:[~2017-02-22 16:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 2:34 [U-Boot] [PATCH 1/2] arm64: booti: update "res1" field to "flags" Masahiro Yamada
2017-02-22 2:34 ` [U-Boot] [PATCH 2/2] arm64: booti: allow to place kernel image anywhere in physical memory Masahiro Yamada
2017-02-22 16:19 ` Tom Rini [this message]
2017-02-23 9:17 ` Masahiro Yamada
2017-02-23 15:31 ` Tom Rini
2017-02-26 22:41 ` Tom Rini
2017-02-28 17:03 ` Masahiro Yamada
2017-02-28 17:15 ` Tom Rini
2017-03-07 11:43 ` Mark Rutland
2017-03-07 12:16 ` Tom Rini
2017-03-07 13:54 ` Mark Rutland
2017-03-07 14:12 ` Tom Rini
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=20170222161921.GS27120@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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