From: "Xiong Yining" <xiongyining1480@phytium.com.cn>
To: devel@edk2.groups.io
Cc: quic_llindhol@quicinc.com, ardb+tianocore@kernel.org,
graeme@xora.org.uk, marcin.juszkiewicz@linaro.org,
chenbaozi@phytium.com.cn,
Xiong Yining <xiongyining1480@phytium.com.cn>
Subject: [edk2-devel] [PATCH v4 0/1] support multi memory nodes
Date: Wed, 27 Mar 2024 14:01:42 +0000 [thread overview]
Message-ID: <20240327140143.3802632-1-xiongyining1480@phytium.com.cn> (raw)
When SaSbQemu platform is configured with multi memory nodes, like
numa architecture, os will ignore any memory node in the device tree
except the first one. The kernel reads UEFI memory map for memory
information when booting via UEFI.
However UEFI only allocates the first memory node memory space for
SbsaQemu platform, in this scenario we can refer to the implement
of "OvmfPkg/Fdt/HighMemDxe" and use the GCD services to add memory
spaces for high memory node.
Instead of using FdtClientDxe driver to get the informatin of memory,
we get the hardware information of memory via SMC calls, which is proposed
on get rid of DeviceTree from SbsaQemu:
https://openfw.io/edk2-devel/20240131132400.3022662-1-xiongyining1480@phytium.com.cn/
Changes in v4:
- Rename SbsaQemuHardwareInfoLib to HardwareInfoLib and use newer function names.
- Link to v3: https://openfw.io/edk2-devel/20240220073332.3249289-1-xiongyining1480@phytium.com.cn/
Changes in v3:
- when the memory node is the first one, there is no need to add it.
Changes in v2:
- get the information of memory via SMC rather than FdtClientDxe.
- add a new driver rather than use HighMemDxe.
Xiong Yining (1):
SbsaQemu: add memory space for the high memory nodes
Platform/Qemu/SbsaQemu/SbsaQemu.dsc | 1 +
Platform/Qemu/SbsaQemu/SbsaQemu.fdf | 1 +
.../SbsaQemuHighMemDxe/SbsaQemuHighMemDxe.inf | 45 ++++++
.../SbsaQemuHighMemDxe/SbsaQemuHighMemDxe.c | 134 ++++++++++++++++++
4 files changed, 181 insertions(+)
create mode 100644 Silicon/Qemu/SbsaQemu/Drivers/SbsaQemuHighMemDxe/SbsaQemuHighMemDxe.inf
create mode 100644 Silicon/Qemu/SbsaQemu/Drivers/SbsaQemuHighMemDxe/SbsaQemuHighMemDxe.c
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#117169): https://edk2.groups.io/g/devel/message/117169
Mute This Topic: https://groups.io/mt/105177587/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~2024-03-27 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 14:01 Xiong Yining [this message]
2024-03-27 14:01 ` [edk2-devel] [PATCH v4 1/1] SbsaQemu: add memory space for the high memory nodes Xiong Yining
2024-03-28 13:18 ` Leif Lindholm
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-list 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=20240327140143.3802632-1-xiongyining1480@phytium.com.cn \
--to=devel@edk2.groups.io \
/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