SbsaQemu can configure with numa-related arguments, but OS cannot identify the numa architecture without SRAT tables. We add supporting for generating SRAT tables at runtime to solve this issue.
the numa-related information and memory information can be obtained via SMC calls which is provided on the EDK2 patch "get rid of DeviceTree from SbsaQemu" https://openfw.io/edk2-devel/20240131132400.3022662-1-xiongyining1...@phytium.com.cn/ when this patch is applied, there is only the first memory node can be identified by OS, this is because UEFI only allocates the first memory node memory space for SbsaQemu platform. we can use patch "Support multi memory nodes" to solve it. Changes in v4: - rename variable names. - Link to v3 https://openfw.io/edk2-devel/20240327135934.3802327-1-xiongyining1...@phytium.com.cn/ changes in v3: - Rename SbsaQemuHardwareInfoLib to HardwareInfoLib and use newer function names. - modify the condition for creating SRAT tables from node greater than 0 to node greater than 1 because we think it's UMA architecture when node is equal to 1. - Link to v2: https://openfw.io/edk2-devel/20240220074736.3249691-1-xiongyining1...@phytium.com.cn/ changes in v2: - fix the compile error which is caused by redundant "+" in SbsaQemuAcpiDxe.h. Xiong Yining (1): SbsaQemu: AcpiDxe: Create SRAT table at runtime .../Drivers/SbsaQemuAcpiDxe/SbsaQemuAcpiDxe.h | 27 ++++++ .../Include/Library/HardwareInfoLib.h | 10 ++ .../Drivers/SbsaQemuAcpiDxe/SbsaQemuAcpiDxe.c | 92 +++++++++++++++++++ .../SbsaQemuHardwareInfoLib.c | 36 ++++++++ 4 files changed, 165 insertions(+) -- 2.34.1 -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#117193): https://edk2.groups.io/g/devel/message/117193 Mute This Topic: https://groups.io/mt/105192388/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
