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 0/2] x86: add support for reserved memory defined by DT
Date: Fri, 13 Mar 2026 16:03:45 +0000 [thread overview]
Message-ID: <20260313160347.2843005-1-jaszczyk@google.com> (raw)
Currently x86 allows to boot with ACPI and DT at the same time and basic DT
support is already in place but processing DT reserved memory was missing.
The DT reserved-memory nodes can be present in DT as described in
Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml.
Similar to other architecture, which supports DT, there is a need to
scan and register reserved memory regions on x86 for such nodes. It is required
by drivers (e.g. open-dice driver) to process DT reserved-memory regions.
v3 -> v4:
- Rebased onto latest upstream baseline. Previous series:
https://lore.kernel.org/all/20250618210628.2635891-1-jaszczyk@chromium.org/
- Improved commit logs
- Improved e820__reserve_nomap_region to perform e820__update_table_print only
once
- Fixed e820__reserve_nomap_region by passing region->base instead of truncated
start address and original size, which was wrong
v2 -> v3:
- Patch #1 which extends of/reserved_mem and adds the possibility to register an
arch specific hook was dropped. Instead "x86/e820: reserve corresponding to DT
reserved-memory nomap region" was introduced.
- "x86/of: add support for reserved memory defined by DT" stop relying on arch
specific hook. Also calling x86_flattree_get_config was moved and is now called
earlier during memblock setup.
For more info please refer to commit log description and v2 discussion:
https://lore.kernel.org/all/20250418124718.1009563-1-jaszczyk@chromium.org/
Grzegorz Jaszczyk (2):
x86/of: add early setup of DT reserved-memory nodes
x86/e820: reserve corresponding to DT reserved-memory nomap region
arch/x86/include/asm/e820/api.h | 1 +
arch/x86/kernel/devicetree.c | 1 +
arch/x86/kernel/e820.c | 20 ++++++++++++++++++++
arch/x86/kernel/setup.c | 6 ++++--
4 files changed, 26 insertions(+), 2 deletions(-)
--
2.53.0.851.ga537e3e6e9-goog
next 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 Grzegorz Jaszczyk [this message]
2026-03-13 16:03 ` [PATCH v4 1/2] x86/of: add early setup of DT reserved-memory nodes Grzegorz Jaszczyk
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-1-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