From: Frank van der Linden <fllinden@amazon.com>
To: <linux-arm-kernel@lists.infradead.org>, <rppt@kernel.org>,
<robh+dt@kernel.org>, <frowand.list@gmail.com>, <ardb@kernel.org>,
<linux-mm@kvack.org>, <devicetree@vger.kernel.org>,
<linux-efi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kexec@lists.infradead.org>, <catalin.marinas@arm.com>,
<will@kernel.org>
Cc: <geert+renesas@glider.be>, Frank van der Linden <fllinden@amazon.com>
Subject: [PATCH 3/3] efi: enforce usable memory range after reserving regions
Date: Mon, 10 Jan 2022 21:08:09 +0000 [thread overview]
Message-ID: <20220110210809.3528-4-fllinden@amazon.com> (raw)
In-Reply-To: <20220110210809.3528-1-fllinden@amazon.com>
The usable memory range may be restricted through parameters that
did not come from EFI, like the FDT "linux,usable-memory-range"
property.
Enforce this range after the EFI memory map regions have been
processed.
Signed-off-by: Frank van der Linden <fllinden@amazon.com>
---
drivers/firmware/efi/efi-init.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/firmware/efi/efi-init.c b/drivers/firmware/efi/efi-init.c
index b19ce1a83f91..280e9178c7df 100644
--- a/drivers/firmware/efi/efi-init.c
+++ b/drivers/firmware/efi/efi-init.c
@@ -204,6 +204,13 @@ static __init void reserve_regions(void)
memblock_reserve(paddr, size);
}
}
+
+ /*
+ * Done, filter !nomap memory we just added so that the
+ * usable range is enforced. This is normally only set
+ * for crash kernels on some architectures.
+ */
+ memblock_enforce_usable_range();
}
void __init efi_init(void)
--
2.32.0
prev parent reply other threads:[~2022-01-10 21:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 21:08 [PATCH 0/3] usable memory range fixes (arm64/fdt/efi) Frank van der Linden
2022-01-10 21:08 ` [PATCH 1/3] memblock: define functions to set the usable memory range Frank van der Linden
2022-01-11 10:31 ` Mike Rapoport
2022-01-11 20:44 ` Frank van der Linden
2022-01-12 18:05 ` Mike Rapoport
2022-01-13 17:33 ` Mike Rapoport
2022-01-14 0:10 ` Frank van der Linden
2022-01-14 0:22 ` Frank van der Linden
2022-01-14 23:27 ` Frank van der Linden
2022-01-24 21:05 ` Frank van der Linden
2022-01-29 16:19 ` Ard Biesheuvel
2022-01-10 21:08 ` [PATCH 2/3] of: fdt: use memblock usable range interface Frank van der Linden
2022-01-10 21:08 ` Frank van der Linden [this message]
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=20220110210809.3528-4-fllinden@amazon.com \
--to=fllinden@amazon.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert+renesas@glider.be \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=robh+dt@kernel.org \
--cc=rppt@kernel.org \
--cc=will@kernel.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