From: timur@codeaurora.org (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [v2] arm64: efi: make sure vmlinux load address aligned on 2MB
Date: Wed, 28 Oct 2015 13:12:36 -0500 [thread overview]
Message-ID: <56311014.9020400@codeaurora.org> (raw)
In-Reply-To: <20151028180836.GB26777@leverpostej>
On 10/28/2015 01:08 PM, Mark Rutland wrote:
> arm64: efi: ensure kernel is loaded at correct address
>
> The kernel image needs to be loaded text_offset_bytes from a 2M-aligned
> base, per Documentation/arm64/booting.txt. If loaded at the wrong offset
> modulo 2M, __create_page_tables will create incorrect page tables.
>
> The EFI stub implicitly assumes that dram_base (i.e. the lowest address
> with a EFI_MEMORY_WB attribute) is 2M-aligned, and tries to load the
> kernel at dram_base + TEXT_OFFSET. If dram_base is not 2M-aligned, the
> kernel will be loaded at the wrong offset from 2M.
Thanks, I'll use that. I messed up a couple other things, so I need to
send out a v3 anyway.
>> - *image_addr = *reserve_addr = dram_base + TEXT_OFFSET;
>> + *image_addr = *reserve_addr =
>> + round_up(dram_base, SZ_2M) + TEXT_OFFSET;
>
> We also need to fix the test for whether we need to relocate the kernel:
> (*image_addr != (dram_base + TEXT_OFFSET)).
>
> When dram_base is not 2M aligned, that is broken, and it's been broken
> since it was introduced in commit 3c7f255039a2ad6e ("arm64: efi: add EFI
> stub") in v3.16.
>
> It's a bit hideous to fix the general case, though, it seems.
Um, so I should I do something more in my v3 patch, or is this a change
for a different patch?
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2015-10-28 18:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 17:37 [PATCH] [v2] arm64: efi: make sure vmlinux load address aligned on 2MB Timur Tabi
2015-10-28 18:08 ` Mark Rutland
2015-10-28 18:12 ` Timur Tabi [this message]
2015-10-28 18:21 ` Mark Rutland
2015-10-29 2:59 ` Ard Biesheuvel
2015-10-29 13:43 ` Mark Rutland
2015-10-29 13:48 ` Ard Biesheuvel
2015-10-29 14:54 ` Timur Tabi
2015-10-29 15:08 ` Ard Biesheuvel
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=56311014.9020400@codeaurora.org \
--to=timur@codeaurora.org \
--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).