From: takahiro.akashi@linaro.org (AKASHI Takahiro) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v27 2/9] arm64: limit memory regions based on DT property, usable-memory-range Date: Wed, 2 Nov 2016 13:52:43 +0900 [thread overview] Message-ID: <20161102045249.12058-1-takahiro.akashi@linaro.org> (raw) In-Reply-To: <20161102044959.11954-1-takahiro.akashi@linaro.org> Crash dump kernel utilizes only a subset of available memory as System RAM. On arm64 kdump, This memory range is advertized to crash dump kernel via a device-tree property under /chosen, linux,usable-memory-range = <BASE SIZE> Crash dump kernel reads this property at boot time and calls memblock_cap_memory_range() to limit usable memory ranges which are described as entries in UEFI memory map table or "memory" nodes in a device tree blob. Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org> Reviewed-by: Geoff Levand <geoff@infradead.org> --- arch/arm64/mm/init.c | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c index 212c4d1..65f1241 100644 --- a/arch/arm64/mm/init.c +++ b/arch/arm64/mm/init.c @@ -187,10 +187,45 @@ static int __init early_mem(char *p) } early_param("mem", early_mem); +static int __init early_init_dt_scan_usablemem(unsigned long node, + const char *uname, int depth, void *data) +{ + struct memblock_region *usablemem = (struct memblock_region *)data; + const __be32 *reg; + int len; + + usablemem->size = 0; + + if (depth != 1 || strcmp(uname, "chosen") != 0) + return 0; + + reg = of_get_flat_dt_prop(node, "linux,usable-memory-range", &len); + if (!reg || (len < (dt_root_addr_cells + dt_root_size_cells))) + return 1; + + usablemem->base = dt_mem_next_cell(dt_root_addr_cells, ®); + usablemem->size = dt_mem_next_cell(dt_root_size_cells, ®); + + return 1; +} + +static void __init fdt_enforce_memory_region(void) +{ + struct memblock_region reg; + + of_scan_flat_dt(early_init_dt_scan_usablemem, ®); + + if (reg.size) + memblock_cap_memory_range(reg.base, reg.size); +} + void __init arm64_memblock_init(void) { const s64 linear_region_size = -(s64)PAGE_OFFSET; + /* Handle linux,usable-memory-range property */ + fdt_enforce_memory_region(); + /* * Ensure that the linear region takes up exactly half of the kernel * virtual address space. This way, we can distinguish a linear address -- 2.10.0
WARNING: multiple messages have this Message-ID (diff)
From: AKASHI Takahiro <takahiro.akashi@linaro.org> To: catalin.marinas@arm.com, will.deacon@arm.com Cc: mark.rutland@arm.com, geoff@infradead.org, kexec@lists.infradead.org, AKASHI Takahiro <takahiro.akashi@linaro.org>, james.morse@arm.com, bauerman@linux.vnet.ibm.com, dyoung@redhat.com, linux-arm-kernel@lists.infradead.org Subject: [PATCH v27 2/9] arm64: limit memory regions based on DT property, usable-memory-range Date: Wed, 2 Nov 2016 13:52:43 +0900 [thread overview] Message-ID: <20161102045249.12058-1-takahiro.akashi@linaro.org> (raw) In-Reply-To: <20161102044959.11954-1-takahiro.akashi@linaro.org> Crash dump kernel utilizes only a subset of available memory as System RAM. On arm64 kdump, This memory range is advertized to crash dump kernel via a device-tree property under /chosen, linux,usable-memory-range = <BASE SIZE> Crash dump kernel reads this property at boot time and calls memblock_cap_memory_range() to limit usable memory ranges which are described as entries in UEFI memory map table or "memory" nodes in a device tree blob. Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org> Reviewed-by: Geoff Levand <geoff@infradead.org> --- arch/arm64/mm/init.c | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c index 212c4d1..65f1241 100644 --- a/arch/arm64/mm/init.c +++ b/arch/arm64/mm/init.c @@ -187,10 +187,45 @@ static int __init early_mem(char *p) } early_param("mem", early_mem); +static int __init early_init_dt_scan_usablemem(unsigned long node, + const char *uname, int depth, void *data) +{ + struct memblock_region *usablemem = (struct memblock_region *)data; + const __be32 *reg; + int len; + + usablemem->size = 0; + + if (depth != 1 || strcmp(uname, "chosen") != 0) + return 0; + + reg = of_get_flat_dt_prop(node, "linux,usable-memory-range", &len); + if (!reg || (len < (dt_root_addr_cells + dt_root_size_cells))) + return 1; + + usablemem->base = dt_mem_next_cell(dt_root_addr_cells, ®); + usablemem->size = dt_mem_next_cell(dt_root_size_cells, ®); + + return 1; +} + +static void __init fdt_enforce_memory_region(void) +{ + struct memblock_region reg; + + of_scan_flat_dt(early_init_dt_scan_usablemem, ®); + + if (reg.size) + memblock_cap_memory_range(reg.base, reg.size); +} + void __init arm64_memblock_init(void) { const s64 linear_region_size = -(s64)PAGE_OFFSET; + /* Handle linux,usable-memory-range property */ + fdt_enforce_memory_region(); + /* * Ensure that the linear region takes up exactly half of the kernel * virtual address space. This way, we can distinguish a linear address -- 2.10.0 _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2016-11-02 4:52 UTC|newest] Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-11-02 4:49 [PATCH v27 0/9] arm64: add kdump support AKASHI Takahiro 2016-11-02 4:49 ` AKASHI Takahiro 2016-11-02 4:51 ` [PATCH v27 1/9] memblock: add memblock_cap_memory_range() AKASHI Takahiro 2016-11-02 4:51 ` AKASHI Takahiro 2016-11-02 4:51 ` AKASHI Takahiro 2016-11-10 17:27 ` Will Deacon 2016-11-10 17:27 ` Will Deacon 2016-11-10 17:27 ` Will Deacon 2016-11-11 2:50 ` AKASHI Takahiro 2016-11-11 2:50 ` AKASHI Takahiro 2016-11-11 2:50 ` AKASHI Takahiro 2016-11-11 3:19 ` Dennis Chen 2016-11-11 3:19 ` Dennis Chen 2016-11-11 3:19 ` Dennis Chen 2016-11-14 5:55 ` AKASHI Takahiro 2016-11-14 5:55 ` AKASHI Takahiro 2016-11-14 5:55 ` AKASHI Takahiro 2016-11-16 16:30 ` Will Deacon 2016-11-16 16:30 ` Will Deacon 2016-11-16 16:30 ` Will Deacon 2016-11-17 5:34 ` AKASHI Takahiro 2016-11-17 5:34 ` AKASHI Takahiro 2016-11-17 5:34 ` AKASHI Takahiro 2016-11-17 11:19 ` Will Deacon 2016-11-17 11:19 ` Will Deacon 2016-11-17 11:19 ` Will Deacon 2016-11-17 18:00 ` James Morse 2016-11-17 18:00 ` James Morse 2016-11-17 18:00 ` James Morse 2016-11-18 1:03 ` AKASHI Takahiro 2016-11-18 1:03 ` AKASHI Takahiro 2016-11-18 1:03 ` AKASHI Takahiro 2016-11-18 12:10 ` Will Deacon 2016-11-18 12:10 ` Will Deacon 2016-11-18 12:10 ` Will Deacon 2016-11-02 4:52 ` AKASHI Takahiro [this message] 2016-11-02 4:52 ` [PATCH v27 2/9] arm64: limit memory regions based on DT property, usable-memory-range AKASHI Takahiro 2016-11-02 4:52 ` [PATCH v27 3/9] arm64: kdump: reserve memory for crash dump kernel AKASHI Takahiro 2016-11-02 4:52 ` AKASHI Takahiro 2016-11-02 4:52 ` [PATCH v27 4/9] arm64: kdump: implement machine_crash_shutdown() AKASHI Takahiro 2016-11-02 4:52 ` AKASHI Takahiro 2016-11-02 4:52 ` [PATCH v27 5/9] arm64: kdump: add VMCOREINFO's for user-space tools AKASHI Takahiro 2016-11-02 4:52 ` AKASHI Takahiro 2016-11-02 4:52 ` [PATCH v27 6/9] arm64: kdump: provide /proc/vmcore file AKASHI Takahiro 2016-11-02 4:52 ` AKASHI Takahiro 2016-11-02 4:52 ` [PATCH v27 7/9] arm64: kdump: enable kdump in defconfig AKASHI Takahiro 2016-11-02 4:52 ` AKASHI Takahiro 2016-11-02 4:52 ` [PATCH v27 8/9] Documentation: kdump: describe arm64 port AKASHI Takahiro 2016-11-02 4:52 ` AKASHI Takahiro [not found] ` <20161102044959.11954-1-takahiro.akashi-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> 2016-11-02 4:54 ` [PATCH v27 9/9] Documentation: dt: chosen properties for arm64 kdump AKASHI Takahiro 2016-11-02 4:54 ` AKASHI Takahiro 2016-11-02 4:54 ` AKASHI Takahiro 2016-11-02 9:39 ` [PATCH v27 0/9] arm64: add kdump support Pratyush Anand 2016-11-02 9:39 ` Pratyush Anand 2016-11-04 3:00 ` AKASHI Takahiro 2016-11-04 3:00 ` AKASHI Takahiro 2016-11-10 16:06 ` James Morse 2016-11-10 16:06 ` James Morse
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=20161102045249.12058-1-takahiro.akashi@linaro.org \ --to=takahiro.akashi@linaro.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.