public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Grzegorz Jaszczyk <jaszczyk@chromium.org>
To: tglx@linutronix.de, robh@kernel.org
Cc: mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
	x86@kernel.org, hpa@zytor.com, saravanak@google.com,
	dmaluka@chromium.org, bgrzesik@google.com, jaszczyk@google.com,
	ilpo.jarvinen@linux.intel.com, usamaarif642@gmail.com,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	tnowicki@google.com, mazurekm@google.com, vineethrp@google.com,
	rppt@kernel.org, agordeev@linux.ibm.com, dyoung@redhat.com,
	myrrhperiwinkle@qtmlabs.xyz, guoweikang.kernel@gmail.com,
	kirill.shutemov@linux.intel.com, akpm@linux-foundation.org,
	joel.granados@kernel.org, sourabhjain@linux.ibm.com
Subject: [PATCH v4 1/2] x86/of: add early setup of DT reserved-memory nodes
Date: Fri, 13 Mar 2026 16:03:46 +0000	[thread overview]
Message-ID: <20260313160347.2843005-2-jaszczyk@google.com> (raw)
In-Reply-To: <20260313160347.2843005-1-jaszczyk@google.com>

The x86 allows booting with ACPI and DT simultaneously, and while basic
DT support is present, the processing of DT 'reserved-memory' is
currently missing.

Some drivers (such as open-dice driver) rely on the standard device-tree
bindings (Documentation/devicetree/bindings/reserved-memory/) to
communicate securely reserved memory region.

To support this add early_init_fdt_scan_reserved_mem as part of early
flattened device tree parsing.

Additionally this patch changes the sequence and calls
x86_flattree_get_config earlier in `setup_arch()`, just after e820
memblock setup, so the DT reserved-memory can be properly reflected in
the memblock before that reserved-memory is used for allocation.

Signed-off-by: Grzegorz Jaszczyk <jaszczyk@google.com>
---
 arch/x86/kernel/devicetree.c | 1 +
 arch/x86/kernel/setup.c      | 4 ++--
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/arch/x86/kernel/devicetree.c b/arch/x86/kernel/devicetree.c
index dd8748c45529..f7db0e8f9c3e 100644
--- a/arch/x86/kernel/devicetree.c
+++ b/arch/x86/kernel/devicetree.c
@@ -307,6 +307,7 @@ void __init x86_flattree_get_config(void)
 		}
 
 		early_init_dt_verify(dt, __pa(dt));
+		early_init_fdt_scan_reserved_mem();
 	}
 
 	unflatten_and_copy_device_tree();
diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index eebcc9db1a1b..cf6c93f8be1a 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -1076,6 +1076,8 @@ void __init setup_arch(char **cmdline_p)
 
 	e820__memblock_setup();
 
+	x86_flattree_get_config();
+
 	/*
 	 * Needs to run after memblock setup because it needs the physical
 	 * memory size.
@@ -1186,8 +1188,6 @@ void __init setup_arch(char **cmdline_p)
 	early_acpi_boot_init();
 	x86_init.mpparse.early_parse_smp_cfg();
 
-	x86_flattree_get_config();
-
 	initmem_init();
 	dma_contiguous_reserve(max_pfn_mapped << PAGE_SHIFT);
 
-- 
2.53.0.851.ga537e3e6e9-goog


  reply	other threads:[~2026-03-13 16:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 16:03 [PATCH v4 0/2] x86: add support for reserved memory defined by DT Grzegorz Jaszczyk
2026-03-13 16:03 ` Grzegorz Jaszczyk [this message]
2026-03-13 16:03 ` [PATCH v4 2/2] x86/e820: reserve corresponding to DT reserved-memory nomap region Grzegorz Jaszczyk

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=20260313160347.2843005-2-jaszczyk@google.com \
    --to=jaszczyk@chromium.org \
    --cc=agordeev@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=bgrzesik@google.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaluka@chromium.org \
    --cc=dyoung@redhat.com \
    --cc=guoweikang.kernel@gmail.com \
    --cc=hpa@zytor.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jaszczyk@google.com \
    --cc=joel.granados@kernel.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mazurekm@google.com \
    --cc=mingo@redhat.com \
    --cc=myrrhperiwinkle@qtmlabs.xyz \
    --cc=robh@kernel.org \
    --cc=rppt@kernel.org \
    --cc=saravanak@google.com \
    --cc=sourabhjain@linux.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=tnowicki@google.com \
    --cc=usamaarif642@gmail.com \
    --cc=vineethrp@google.com \
    --cc=x86@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