From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Gerd Hoffmann" <kraxel@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Ani Sinha" <ani@anisinha.ca>,
"Igor Mammedov" <imammedo@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [PATCH 2/6] bios-tables-test: use 128M numa nodes on aarch64
Date: Thu, 16 Mar 2023 10:54:28 +0100 [thread overview]
Message-ID: <20230316095432.1514080-3-kraxel@redhat.com> (raw)
In-Reply-To: <20230316095432.1514080-1-kraxel@redhat.com>
Recent edk2 versions don't boot with very small numa nodes.
Bump the size from 64M to 128M.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
tests/qtest/bios-tables-test.c | 6 +++---
tests/data/acpi/virt/SRAT.acpihmatvirt | Bin 240 -> 240 bytes
tests/data/acpi/virt/SSDT.memhp | Bin 1817 -> 1817 bytes
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/tests/qtest/bios-tables-test.c b/tests/qtest/bios-tables-test.c
index 76d510091177..873358943784 100644
--- a/tests/qtest/bios-tables-test.c
+++ b/tests/qtest/bios-tables-test.c
@@ -1679,9 +1679,9 @@ static void test_acpi_virt_tcg_acpi_hmat(void)
test_acpi_one(" -machine hmat=on"
" -cpu cortex-a57"
" -smp 4,sockets=2"
- " -m 256M"
- " -object memory-backend-ram,size=64M,id=ram0"
- " -object memory-backend-ram,size=64M,id=ram1"
+ " -m 384M"
+ " -object memory-backend-ram,size=128M,id=ram0"
+ " -object memory-backend-ram,size=128M,id=ram1"
" -object memory-backend-ram,size=128M,id=ram2"
" -numa node,nodeid=0,memdev=ram0"
" -numa node,nodeid=1,memdev=ram1"
diff --git a/tests/data/acpi/virt/SRAT.acpihmatvirt b/tests/data/acpi/virt/SRAT.acpihmatvirt
index 691ef56e34bc84509270db316d908f5979c209bb..6fe55dd7d07fef0f8fe16a209e96a89dd48ca240 100644
GIT binary patch
delta 67
zcmeys_<@ltILI;N0|NsC^R$Uvjf@-<d*mlxmepX?U;>JPK>(EIfYJ<%Fb0qY0P4I6
AJ^%m!
delta 59
zcmeys_<@ltILI;N0|NsC^Qwtljf^Z4d*l^dfLst@flv$#j4%d}X4GJsxL6ecZ+{66
diff --git a/tests/data/acpi/virt/SSDT.memhp b/tests/data/acpi/virt/SSDT.memhp
index 2fcfc5fda955dc4ba78a5f4116eed99ec7202fbd..ef93c44464f1fe38f7e5babd5d67f345cc6363a6 100644
GIT binary patch
delta 22
dcmbQqH<OPmIM^jblAVEpap^`bUUsI7&Hz1t1wsG-
delta 22
dcmbQqH<OPmIM^jblAVEpv2i08FFVs$X8=5?1wsG-
--
2.39.2
next prev parent reply other threads:[~2023-03-16 9:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 9:54 [PATCH 0/6] edk2: update to 2023-02 stable tag Gerd Hoffmann
2023-03-16 9:54 ` [PATCH 1/6] acpi: enable tests/data/acpi updates Gerd Hoffmann
2023-03-16 9:54 ` Gerd Hoffmann [this message]
2023-03-28 12:03 ` [PATCH 2/6] bios-tables-test: use 128M numa nodes on aarch64 Igor Mammedov
2023-03-28 12:09 ` Daniel P. Berrangé
2023-03-28 12:28 ` Igor Mammedov
2023-03-16 9:54 ` [PATCH 3/6] acpi: disable tests/data/acpi updates Gerd Hoffmann
2023-03-16 9:54 ` [PATCH 4/6] edk2: update submodule to edk2-stable202302 Gerd Hoffmann
2023-03-16 10:50 ` Philippe Mathieu-Daudé
2023-03-16 9:54 ` [PATCH 5/6] edk2: replace build scripts Gerd Hoffmann
2023-03-16 9:54 ` [PATCH 6/6] edk2: update firmware binaries Gerd Hoffmann
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=20230316095432.1514080-3-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=ani@anisinha.ca \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).