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 2/3] of: fdt: use memblock usable range interface
Date: Mon, 10 Jan 2022 21:08:08 +0000 [thread overview]
Message-ID: <20220110210809.3528-3-fllinden@amazon.com> (raw)
In-Reply-To: <20220110210809.3528-1-fllinden@amazon.com>
Use the memblock usable range interface to set and enforce the
usable memory range (if any).
Signed-off-by: Frank van der Linden <fllinden@amazon.com>
---
drivers/of/fdt.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
index 4546572af24b..b3c2a4124518 100644
--- a/drivers/of/fdt.c
+++ b/drivers/of/fdt.c
@@ -1279,7 +1279,8 @@ void __init early_init_dt_scan_nodes(void)
of_scan_flat_dt(early_init_dt_scan_memory, NULL);
/* Handle linux,usable-memory-range property */
- memblock_cap_memory_range(cap_mem_addr, cap_mem_size);
+ memblock_set_usable_range(cap_mem_addr, cap_mem_size);
+ memblock_enforce_usable_range();
}
bool __init early_init_dt_scan(void *params)
--
2.32.0
WARNING: multiple messages have this Message-ID (diff)
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 2/3] of: fdt: use memblock usable range interface
Date: Mon, 10 Jan 2022 21:08:08 +0000 [thread overview]
Message-ID: <20220110210809.3528-3-fllinden@amazon.com> (raw)
In-Reply-To: <20220110210809.3528-1-fllinden@amazon.com>
Use the memblock usable range interface to set and enforce the
usable memory range (if any).
Signed-off-by: Frank van der Linden <fllinden@amazon.com>
---
drivers/of/fdt.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
index 4546572af24b..b3c2a4124518 100644
--- a/drivers/of/fdt.c
+++ b/drivers/of/fdt.c
@@ -1279,7 +1279,8 @@ void __init early_init_dt_scan_nodes(void)
of_scan_flat_dt(early_init_dt_scan_memory, NULL);
/* Handle linux,usable-memory-range property */
- memblock_cap_memory_range(cap_mem_addr, cap_mem_size);
+ memblock_set_usable_range(cap_mem_addr, cap_mem_size);
+ memblock_enforce_usable_range();
}
bool __init early_init_dt_scan(void *params)
--
2.32.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Frank van der Linden <fllinden@amazon.com>
To: kexec@lists.infradead.org
Subject: [PATCH 2/3] of: fdt: use memblock usable range interface
Date: Mon, 10 Jan 2022 21:08:08 +0000 [thread overview]
Message-ID: <20220110210809.3528-3-fllinden@amazon.com> (raw)
In-Reply-To: <20220110210809.3528-1-fllinden@amazon.com>
Use the memblock usable range interface to set and enforce the
usable memory range (if any).
Signed-off-by: Frank van der Linden <fllinden@amazon.com>
---
drivers/of/fdt.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
index 4546572af24b..b3c2a4124518 100644
--- a/drivers/of/fdt.c
+++ b/drivers/of/fdt.c
@@ -1279,7 +1279,8 @@ void __init early_init_dt_scan_nodes(void)
of_scan_flat_dt(early_init_dt_scan_memory, NULL);
/* Handle linux,usable-memory-range property */
- memblock_cap_memory_range(cap_mem_addr, cap_mem_size);
+ memblock_set_usable_range(cap_mem_addr, cap_mem_size);
+ memblock_enforce_usable_range();
}
bool __init early_init_dt_scan(void *params)
--
2.32.0
next prev parent reply other threads:[~2022-01-10 21:09 UTC|newest]
Thread overview: 39+ 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 ` Frank van der Linden
2022-01-10 21:08 ` 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-10 21:08 ` Frank van der Linden
2022-01-10 21:08 ` Frank van der Linden
2022-01-11 10:31 ` Mike Rapoport
2022-01-11 10:31 ` Mike Rapoport
2022-01-11 10:31 ` Mike Rapoport
2022-01-11 20:44 ` Frank van der Linden
2022-01-11 20:44 ` Frank van der Linden
2022-01-11 20:44 ` Frank van der Linden
2022-01-12 18:05 ` Mike Rapoport
2022-01-12 18:05 ` Mike Rapoport
2022-01-12 18:05 ` Mike Rapoport
2022-01-13 17:33 ` Mike Rapoport
2022-01-13 17:33 ` Mike Rapoport
2022-01-13 17:33 ` Mike Rapoport
2022-01-14 0:10 ` Frank van der Linden
2022-01-14 0:10 ` Frank van der Linden
2022-01-14 0:10 ` Frank van der Linden
2022-01-14 0:22 ` Frank van der Linden
2022-01-14 0:22 ` Frank van der Linden
2022-01-14 0:22 ` Frank van der Linden
2022-01-14 23:27 ` Frank van der Linden
2022-01-14 23:27 ` Frank van der Linden
2022-01-14 23:27 ` Frank van der Linden
2022-01-24 21:05 ` Frank van der Linden
2022-01-24 21:05 ` Frank van der Linden
2022-01-24 21:05 ` Frank van der Linden
2022-01-29 16:19 ` Ard Biesheuvel
2022-01-29 16:19 ` Ard Biesheuvel
2022-01-29 16:19 ` Ard Biesheuvel
2022-01-10 21:08 ` Frank van der Linden [this message]
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
2022-01-10 21:08 ` [PATCH 3/3] efi: enforce usable memory range after reserving regions Frank van der Linden
2022-01-10 21:08 ` Frank van der Linden
2022-01-10 21:08 ` Frank van der Linden
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-3-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 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.