[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250417221938.579452-1-jaszczyk@chromium.org>
Date: Thu, 17 Apr 2025 22:19:36 +0000
From: Grzegorz Jaszczyk <jaszczyk@...omium.org>
To: tglx@...utronix.de,
robh@...nel.org
Cc: mingo@...hat.com,
bp@...en8.de,
dave.hansen@...ux.intel.com,
x86@...nel.org,
hpa@...or.com,
saravanak@...gle.com,
dmaluka@...omium.org,
bgrzesik@...gle.com,
jaszczyk@...gle.com,
ilpo.jarvinen@...ux.intel.com,
usamaarif642@...il.com,
linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org,
tnowicki@...gle.com,
mazurekm@...gle.com,
vineethrp@...gle.com
Subject: [PATCH 0/2] x86: add support for reserved memory defined by DT
From: Grzegorz Jaszczyk <jaszczyk@...gle.com>
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.
Patch #1 extends of/reserved_mem and adds the possibility to register an arch
specific hook, which will allow to validate if reserved-memory region passed by
DT is valid.
Patch #2, uses introduced in Patch #1 API and registers x86 specific hook, which
will validate if reserved-memory region passed by DT is covered by E820 reserved
region entry.
For more details please refer to the commit log description of individual
patches.
Grzegorz Jaszczyk (2):
of: fdt: allow to register arch specific hook validating reserved
region
x86/of: add support for reserved memory defined by DT
arch/x86/kernel/devicetree.c | 12 ++++++++++++
drivers/of/of_reserved_mem.c | 14 ++++++++++++++
include/linux/of_fdt.h | 4 ++++
3 files changed, 30 insertions(+)
--
2.49.0.805.g082f7c87e0-goog
Powered by blists - more mailing lists