From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>,
Leif Lindholm <leif@nuviainc.com>
Cc: qemu-arm <qemu-arm@nongnu.org>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH] arm: bump amount of PMU counters to pass SBSA ACS
Date: Wed, 3 Mar 2021 21:33:16 +0100 [thread overview]
Message-ID: <95e5a34b-1325-8eb3-25ca-b3e63b4e67a1@linaro.org> (raw)
In-Reply-To: <CAFEAcA-KFF_An50h8JKy68_Y3J4j=kQCOFyGoySKyh53E7KGYg@mail.gmail.com>
W dniu 03.03.2021 o 19:06, Peter Maydell pisze:
> On Wed, 3 Mar 2021 at 17:48, Leif Lindholm <leif@nuviainc.com> wrote:
>> It would be good if we could get 6.0 closer to SBSA compliance.
>
> How far away are we at the moment ?
Hard to tell me how many of those things are missing in QEMU and how
many in EDK2 we use as firmware.
SBSA-ACS failures:
GIC ITS is missing (Shashi Mallela works on it):
102 : If PCIe, then GIC implements ITS : Result: --FAIL-- 1
104 : GIC Maintenance Interrupt : Result: --FAIL-- 1
System timers are not present in GTDT so few more tests are not run:
206 : SYS Timer if PE Timer not ON : Result: --FAIL-- 1
PE Timers are not always-on.
207 : CNTCTLBase & CNTBaseN access : Result: -SKIPPED- 1
No System timers are defined
505 : Wake from System Timer Interrupt : Result: -SKIPPED- 1
No system timers implemented
There is no SMMU present so SMMU and IO virtualization tests are not
run. This one is probably related:
605 : Memory Access to Un-Populated addr: Result: --FAIL-- 1
Memory access check fails at address = 0x104C0000
next prev parent reply other threads:[~2021-03-03 20:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 15:16 [PATCH] arm: bump amount of PMU counters to pass SBSA ACS Marcin Juszkiewicz
2021-03-03 17:48 ` Leif Lindholm
2021-03-03 18:06 ` Peter Maydell
2021-03-03 20:33 ` Marcin Juszkiewicz [this message]
2021-03-04 13:53 ` Leif Lindholm
2021-03-04 15:14 ` Peter Maydell
2021-03-04 15:25 ` Leif Lindholm
2021-03-11 17:02 ` Peter Maydell
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=95e5a34b-1325-8eb3-25ca-b3e63b4e67a1@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--cc=leif@nuviainc.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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).