public inbox for
 help / color / mirror / Atom feed
From: "Xiong Yining" <>
	Xiong Yining <>
Subject: [edk2-devel] [PATCH v4 0/1] Add support for generating SRAT tables
Date: Thu, 28 Mar 2024 06:19:34 +0000	[thread overview]
Message-ID: <> (raw)

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 

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

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:

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(+)


-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group.
View/Reply Online (#117193):
Mute This Topic:
Group Owner:
Unsubscribe: []

             reply	other threads:[~2024-03-28  6:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28  6:19 Xiong Yining [this message]
2024-03-28  6:19 ` [edk2-devel] [PATCH v4 1/1] SbsaQemu: AcpiDxe: Create SRAT table at runtime Xiong Yining
2024-03-28 13:24   ` Marcin Juszkiewicz
2024-03-28 13:31   ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \

* 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