From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: catalin.marinas@arm.com, will@kernel.org, rppt@kernel.org
Cc: akpm@linux-foundation.org, david@redhat.com,
anshuman.khandual@arm.com, geert+renesas@glider.be,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-imx@nxp.com,
Peng Fan <peng.fan@nxp.com>
Subject: [PATCH 2/2] arm64: mm: support bootparam max_addr
Date: Wed, 15 Dec 2021 14:45:59 +0800 [thread overview]
Message-ID: <20211215064559.2843555-2-peng.fan@oss.nxp.com> (raw)
In-Reply-To: <20211215064559.2843555-1-peng.fan@oss.nxp.com>
From: Peng Fan <peng.fan@nxp.com>
There is a "mem=[x]" boot parameter, but when there is a whole reserved
by secure TEE, the continuous DRAM area is split with two memblocks.
For example, DRAM area [0x40000000, 0xffffffff], when TEE uses
[0x50000000, 0x51000000), the memblock will be split into
[0x40000000, 0x50000000) and [0x51000000, 0xffffffff].
If pass "mem=1024MB", the actually max addr will be 0x81000000.
However if need the max addr be 0x80000000, mem=1008MB should be used.
There also might be multiple other holes that no visible to Linux, when
we wanna to limit the max addr usable by Linux, using "max_addr=[X]" is
much easier than "mem=[X]"
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
arch/arm64/mm/init.c | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
index db63cc885771..3364b5e7a7fe 100644
--- a/arch/arm64/mm/init.c
+++ b/arch/arm64/mm/init.c
@@ -173,6 +173,7 @@ int pfn_is_map_memory(unsigned long pfn)
EXPORT_SYMBOL(pfn_is_map_memory);
static phys_addr_t memory_limit __ro_after_init = PHYS_ADDR_MAX;
+static phys_addr_t max_addr __ro_after_init = PHYS_ADDR_MAX;
/*
* Limit the memory size that was specified via FDT.
@@ -189,6 +190,18 @@ static int __init early_mem(char *p)
}
early_param("mem", early_mem);
+static int __init set_max_addr(char *p)
+{
+ if (!p)
+ return 1;
+
+ max_addr = memparse(p, &p) & PAGE_MASK;
+ pr_notice("Memory max addr set to 0x%llx\n", max_addr);
+
+ return 0;
+}
+early_param("max_addr", set_max_addr);
+
void __init arm64_memblock_init(void)
{
s64 linear_region_size = PAGE_END - _PAGE_OFFSET(vabits_actual);
@@ -253,6 +266,9 @@ void __init arm64_memblock_init(void)
memblock_add(__pa_symbol(_text), (u64)(_end - _text));
}
+ if (max_addr != PHYS_ADDR_MAX)
+ memblock_cap_memory_range(0, max_addr);
+
if (IS_ENABLED(CONFIG_BLK_DEV_INITRD) && phys_initrd_size) {
/*
* Add back the memory we just removed if it results in the
@@ -427,4 +443,9 @@ void dump_mem_limit(void)
} else {
pr_emerg("Memory Limit: none\n");
}
+
+ if (max_addr != PHYS_ADDR_MAX)
+ pr_emerg("Max addr: 0x%llx\n", max_addr);
+ else
+ pr_emerg("Max addr: none\n");
}
--
2.25.1
next prev parent reply other threads:[~2021-12-15 6:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 6:45 [PATCH 1/2] arm64: mm: apply __ro_after_init to memory_limit Peng Fan (OSS)
2021-12-15 6:45 ` Peng Fan (OSS) [this message]
2021-12-15 7:32 ` [PATCH 2/2] arm64: mm: support bootparam max_addr Ard Biesheuvel
2021-12-15 7:59 ` Peng Fan
2021-12-15 9:24 ` Mike Rapoport
2021-12-15 9:30 ` Peng Fan
2021-12-15 9:53 ` Mike Rapoport
2021-12-15 12:05 ` Peng Fan
2021-12-16 14:19 ` Mike Rapoport
2021-12-15 7:30 ` [PATCH 1/2] arm64: mm: apply __ro_after_init to memory_limit Ard Biesheuvel
2021-12-15 10:02 ` David Hildenbrand
2022-01-20 15:56 ` (subset) " Catalin Marinas
2022-01-21 2:28 ` Anshuman Khandual
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=20211215064559.2843555-2-peng.fan@oss.nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--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
all inboxes | Powered by JetHome®