From: Ard Biesheuvel <ardb@kernel.org>
To: linux-arm-kernel@lists.infradead.org
Cc: Arnd Bergmann <arnd@arndb.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Linus Walleij <linus.walleij@linaro.org>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Alexander Sverdlin <alexander.sverdlin@nokia.com>,
Ard Biesheuvel <ardb@kernel.org>
Subject: [PATCH 0/2] ARM: remove TEXT_OFFSET override for Axxia
Date: Mon, 11 Jan 2021 11:30:18 +0100 [thread overview]
Message-ID: <20210111103020.32372-1-ardb@kernel.org> (raw)
Now that the minimum relative alignment of physical to linear virtual
addresses has been reduced to 2 MiB (from 16 MiB), simply rounding up
the lowest usable DRAM address is no longer as wasteful as before.
Combined with Geert's DT memory discovery patch [0], we can now also
cross reference the decompressor's intended load address against DT memory
reservations, and override it if it points into a reserved area.
By doing this, we remove the need for TEXT_OFFSET hacks that override the
placement of the decompressed kernel on all platforms to accommodate a
single platform that has decided to put reserved areas at the base of DRAM.
As a first step, apply this change to mach-axxia, which is the only platform
that increments TEXT_OFFSET by 3 MiB, and defines this memory reservation as
a /memreserve/ entry.
Future followup work could be done that takes the /reserved-memory node into
account as well, which would allow us to remove another set of TEXT_OFFSET
override hacks for a collection of Qualcomm platforms.
[0] https://lore.kernel.org/linux-arm-kernel/20210104130111.1269694-1-geert+renesas@glider.be/
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Linus Walleij <linus.walleij@linaro.org>
Cc: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Alexander Sverdlin <alexander.sverdlin@nokia.com>
Ard Biesheuvel (2):
ARM: take memreserve FDT entries into account when discovering base of
RAM
ARM: axxia: remove TEXT_OFFSET override hack
arch/arm/Makefile | 1 -
arch/arm/boot/compressed/Makefile | 2 ++
.../arm/boot/compressed/fdt_check_mem_start.c | 35 ++++++++++++++++++-
3 files changed, 36 insertions(+), 2 deletions(-)
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-01-11 10:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 10:30 Ard Biesheuvel [this message]
2021-01-11 10:30 ` [PATCH 1/2] ARM: take memreserve FDT entries into account when discovering base of RAM Ard Biesheuvel
2021-01-11 10:30 ` [PATCH 2/2] ARM: axxia: remove TEXT_OFFSET override hack Ard Biesheuvel
2021-01-12 10:34 ` Alexander Sverdlin
2021-01-12 10:40 ` Ard Biesheuvel
2021-01-12 11:22 ` Alexander Sverdlin
2021-01-12 13:55 ` Alexander Sverdlin
2021-01-12 14:05 ` Ard Biesheuvel
2021-01-12 14:21 ` Alexander Sverdlin
2021-01-13 17:49 ` Ard Biesheuvel
2021-01-13 21:26 ` Russell King - ARM Linux admin
2021-01-13 22:43 ` 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=20210111103020.32372-1-ardb@kernel.org \
--to=ardb@kernel.org \
--cc=alexander.sverdlin@nokia.com \
--cc=arnd@arndb.de \
--cc=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
/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).