From: Chen Zhou <chenzhou10@huawei.com>
To: <tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
<ebiederm@xmission.com>, <rppt@linux.ibm.com>,
<catalin.marinas@arm.com>, <will.deacon@arm.com>,
<akpm@linux-foundation.org>, <ard.biesheuvel@linaro.org>
Cc: <horms@verge.net.au>, <takahiro.akashi@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <kexec@lists.infradead.org>,
<linux-mm@kvack.org>, <wangkefeng.wang@huawei.com>,
Chen Zhou <chenzhou10@huawei.com>
Subject: [PATCH v4 3/5] memblock: add memblock_cap_memory_ranges for multiple ranges
Date: Mon, 15 Apr 2019 18:57:23 +0800 [thread overview]
Message-ID: <20190415105725.22088-4-chenzhou10@huawei.com> (raw)
In-Reply-To: <20190415105725.22088-1-chenzhou10@huawei.com>
The memblock_cap_memory_range() removes all the memory except the
range passed to it. Extend this function to receive memblock_type
with the regions that should be kept.
Enable this function in arm64 for reservation of multiple regions
for the crash kernel.
Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
---
include/linux/memblock.h | 1 +
mm/memblock.c | 45 +++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 46 insertions(+)
diff --git a/include/linux/memblock.h b/include/linux/memblock.h
index 47e3c06..180877c 100644
--- a/include/linux/memblock.h
+++ b/include/linux/memblock.h
@@ -446,6 +446,7 @@ phys_addr_t memblock_start_of_DRAM(void);
phys_addr_t memblock_end_of_DRAM(void);
void memblock_enforce_memory_limit(phys_addr_t memory_limit);
void memblock_cap_memory_range(phys_addr_t base, phys_addr_t size);
+void memblock_cap_memory_ranges(struct memblock_type *regions_to_keep);
void memblock_mem_limit_remove_map(phys_addr_t limit);
bool memblock_is_memory(phys_addr_t addr);
bool memblock_is_map_memory(phys_addr_t addr);
diff --git a/mm/memblock.c b/mm/memblock.c
index f315eca..9661807 100644
--- a/mm/memblock.c
+++ b/mm/memblock.c
@@ -1697,6 +1697,51 @@ void __init memblock_cap_memory_range(phys_addr_t base, phys_addr_t size)
base + size, PHYS_ADDR_MAX);
}
+void __init memblock_cap_memory_ranges(struct memblock_type *regions_to_keep)
+{
+ int start_rgn[INIT_MEMBLOCK_REGIONS], end_rgn[INIT_MEMBLOCK_REGIONS];
+ int i, j, ret, nr = 0;
+ struct memblock_region *regs = regions_to_keep->regions;
+
+ for (i = 0; i < regions_to_keep->cnt; i++) {
+ ret = memblock_isolate_range(&memblock.memory, regs[i].base,
+ regs[i].size, &start_rgn[i], &end_rgn[i]);
+ if (ret)
+ break;
+ nr++;
+ }
+ if (!nr)
+ return;
+
+ /* remove all the MAP regions */
+ for (i = memblock.memory.cnt - 1; i >= end_rgn[nr - 1]; i--)
+ if (!memblock_is_nomap(&memblock.memory.regions[i]))
+ memblock_remove_region(&memblock.memory, i);
+
+ for (i = nr - 1; i > 0; i--)
+ for (j = start_rgn[i] - 1; j >= end_rgn[i - 1]; j--)
+ if (!memblock_is_nomap(&memblock.memory.regions[j]))
+ memblock_remove_region(&memblock.memory, j);
+
+ for (i = start_rgn[0] - 1; i >= 0; i--)
+ if (!memblock_is_nomap(&memblock.memory.regions[i]))
+ memblock_remove_region(&memblock.memory, i);
+
+ /* truncate the reserved regions */
+ memblock_remove_range(&memblock.reserved, 0, regs[0].base);
+
+ for (i = nr - 1; i > 0; i--) {
+ phys_addr_t remove_base = regs[i - 1].base + regs[i - 1].size;
+ phys_addr_t remove_size = regs[i].base - remove_base;
+
+ memblock_remove_range(&memblock.reserved, remove_base,
+ remove_size);
+ }
+
+ memblock_remove_range(&memblock.reserved,
+ regs[nr - 1].base + regs[nr - 1].size, PHYS_ADDR_MAX);
+}
+
void __init memblock_mem_limit_remove_map(phys_addr_t limit)
{
phys_addr_t max_addr;
--
2.7.4
next prev parent reply other threads:[~2019-04-15 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 10:57 [PATCH v4 0/5] support reserving crashkernel above 4G on arm64 kdump Chen Zhou
2019-04-15 10:57 ` [PATCH v4 1/5] x86: kdump: move reserve_crashkernel_low() into kexec_core.c Chen Zhou
2019-04-15 10:57 ` [PATCH v4 2/5] arm64: kdump: support reserving crashkernel above 4G Chen Zhou
2019-04-15 10:57 ` Chen Zhou [this message]
2019-04-15 19:09 ` [PATCH v4 3/5] memblock: add memblock_cap_memory_ranges for multiple ranges Mike Rapoport
2019-04-16 2:55 ` Chen Zhou
2019-04-15 10:57 ` [PATCH v4 4/5] arm64: kdump: support more than one crash kernel regions Chen Zhou
2019-04-15 10:57 ` [PATCH v4 5/5] kdump: update Documentation about crashkernel on arm64 Chen Zhou
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=20190415105725.22088-4-chenzhou10@huawei.com \
--to=chenzhou10@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=rppt@linux.ibm.com \
--cc=takahiro.akashi@linaro.org \
--cc=tglx@linutronix.de \
--cc=wangkefeng.wang@huawei.com \
--cc=will.deacon@arm.com \
/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