From: carl@cog.systems (Carl van Schaik)
To: linux-arm-kernel@lists.infradead.org
Subject: arm64 boot requirements
Date: Mon, 30 Nov 2015 12:45:18 +1100 [thread overview]
Message-ID: <565BAA2E.5090102@cog.systems> (raw)
In commit bd00cd5f8c8c3c282bb1e1eac6a6679a4f808091, the idmap_pg_dir and
swapper_pg_dir where moved from before the kernel to after it.
The problem is that these symbols fall outside the range covered by the
ELF file - outside of any section.
A bootloader which loads the kernel ELF file and dynamically determines
where to place the DTB, may try place it after the kernel. We've just
run into this problem and the DTB gets overwritten as soon as the
pagetables are created.
I'd suggest that the kernel either:
A. document this boot requirement for where not to load a DTB
B. update the vmlinux.lds.S such that these symbols (and _end) are
properly covered by a section in the ELF, and thus preventing this issue.
thanks,
Carl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-arm64-place-initial-page-tables-in-ELF-section.patch
Type: text/x-patch
Size: 1323 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20151130/9de49ebc/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4267 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20151130/9de49ebc/attachment.p7s>
next reply other threads:[~2015-11-30 1:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 1:45 Carl van Schaik [this message]
2015-12-01 11:02 ` arm64 boot requirements Mark Rutland
2015-12-01 11:52 ` Ard Biesheuvel
2015-12-01 22:09 ` Christopher Covington
2015-12-02 10:26 ` Mark Rutland
2015-12-02 13:46 ` Carl van Schaik
2015-12-03 12:24 ` Mark Rutland
2015-12-01 12:50 ` Pratyush Anand
2015-12-02 19:03 ` Geoff Levand
2015-12-03 12:29 ` Mark Rutland
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=565BAA2E.5090102@cog.systems \
--to=carl@cog.systems \
--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).