From: "Marcin Juszkiewicz via groups.io" <marcin=juszkiewicz.com.pl@groups.io>
To: Johnny Lin/WYHQ/Wiwynn <johnny_lin@wiwynn.com>, devel@edk2.groups.io
Subject: Re: [edk2-devel] SbsaQemu: SIP_SVC_GET_CPU_TOPOLOGY call failed (need updated binaries in edk2-non-osi?)
Date: Sun, 23 Mar 2025 13:50:00 +0100 [thread overview]
Message-ID: <aecfa67f-7982-46e7-96e0-abf64c16f800@juszkiewicz.com.pl> (raw)
In-Reply-To: <15989.1742715270038644235@groups.io>
W dniu 23.03.2025 o 08:34, Johnny Lin/WYHQ/Wiwynn via groups.io pisze:
> Has this been fixed? I am seeing the same issue with QEMU emulator
> version 8.0.93.
QemuSbsa needs QEMU 9.x or later. Especially this commit:
==========================
From 3b36cead6ecc0e40edb8b2f3e253baa01ebc1e9a Mon Sep 17 00:00:00 2001
From: Xiong Yining <xiongyining1480@phytium.com.cn>
Date: Fri, 7 Jun 2024 10:38:25 +0000
Subject: [PATCH] hw/arm/sbsa-ref: Enable CPU cluster on ARM sbsa machine
Enable CPU cluster support on SbsaQemu platform, so that users can
specify a 4-level CPU hierarchy sockets/clusters/cores/threads. And
this topology can be passed to the firmware through /cpus/topology
Device Tree.
==========================
Without it we do not have topology information and machine stops.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121215): https://edk2.groups.io/g/devel/message/121215
Mute This Topic: https://groups.io/mt/108224493/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2025-03-23 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 14:36 [edk2-devel] SbsaQemu: SIP_SVC_GET_CPU_TOPOLOGY call failed (need updated binaries in edk2-non-osi?) Rebecca Cran via groups.io
2024-09-02 10:54 ` Marcin Juszkiewicz
[not found] ` <15989.1742715270038644235@groups.io>
2025-03-23 12:50 ` Marcin Juszkiewicz via groups.io [this message]
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=aecfa67f-7982-46e7-96e0-abf64c16f800@juszkiewicz.com.pl \
--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