From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Joel Stanley" <joel@jms.id.au>
Cc: <kvm@vger.kernel.org>, "Laurent Vivier" <lvivier@redhat.com>,
"Thomas Huth" <thuth@redhat.com>, <linuxppc-dev@lists.ozlabs.org>,
<qemu-ppc@nongnu.org>, <qemu-devel@nongnu.org>
Subject: Re: [kvm-unit-tests v4 00/12] powerpc: updates, P10, PNV support
Date: Thu, 15 Jun 2023 13:02:34 +1000 [thread overview]
Message-ID: <CTCW1ILCXTMA.24T7LU9PQBTDA@wheely> (raw)
In-Reply-To: <CACPK8XdpAxjvP+bFNFJzQQzBYvEwsE69QkbNWRumZtUW2wOrrA@mail.gmail.com>
On Wed Jun 14, 2023 at 11:09 AM AEST, Joel Stanley wrote:
> On Thu, 8 Jun 2023 at 07:58, Nicholas Piggin <npiggin@gmail.com> wrote:
> >
> > Posting again, a couple of patches were merged and accounted for review
> > comments from last time.
>
> I saw some failures in the spr tests running on a power9 powernv system:
>
> $ TESTNAME=sprs TIMEOUT=90s ACCEL= ./powerpc/run powerpc/sprs.elf -smp
> 1 |grep FAIL
> FAIL: WORT ( 895): 0x00000000c0deba80 <==> 0x0000000000000000
This is just TCG machine? I'm not sure why WORT fails, AFAIKS it's the
same on POWER8 and doesn't do anything just a simple register. I think
on real hardware WORT may not have any bits implemented on POWER9
though.
> $ MIGRATION=yes TESTNAME=sprs-migration TIMEOUT=90s ACCEL=
> ./powerpc/run powerpc/sprs.elf -smp 1 -append '-w' | grep FAIL
> FAIL: SRR0 ( 26): 0xcafefacec0debabc <==> 0x0000000000402244
> FAIL: SRR1 ( 27): 0xc0000006409ebab6 <==> 0x8000000000001001
> FAIL: CTRL ( 136): 0x00000000 <==> 0x00008001
> FAIL: WORT ( 895): 0x00000000c0deba80 <==> 0x0000000000000000
> FAIL: PIR (1023): 0x00000010 <==> 0x00000049
>
> Linux 6.2.0-20-generic
> QEMU emulator version 7.2.0 (Debian 1:7.2+dfsg-5ubuntu2)
>
> On a power8 powernv:
>
> MIGRATION=yes TESTNAME=sprs-migration TIMEOUT=90s ACCEL= ./powerpc/run
> powerpc/sprs.elf -smp 1 -append '-w' |grep FAIL
> FAIL: SRR0 ( 26): 0xcafefacec0debabc <==> 0x0000000000402234
> FAIL: SRR1 ( 27): 0xc0000006409ebab6 <==> 0x8000000000001000
> FAIL: CTRL ( 136): 0x00000000 <==> 0x00008001
> FAIL: PIR (1023): 0x00000060 <==> 0x00000030
Hmm, seems we take some interrupt over migration test that is not
accounted for (could check the address in SRR0 to see where it is).
Either need to prevent that interrupt or avoid failing on SRR0/1 on
this test.
Interesting about CTRL, I wonder if that not migrating correctly.
PIR looks like a migration issue as well, it can't be changed so
destination CPU has got a different PIR. I would be inclined to
leave those as failing to remind us to look into them.
I'll take a look at the others though.
Thanks,
Nick
next parent reply other threads:[~2023-06-15 3:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230608075826.86217-1-npiggin@gmail.com>
[not found] ` <CACPK8XdpAxjvP+bFNFJzQQzBYvEwsE69QkbNWRumZtUW2wOrrA@mail.gmail.com>
2023-06-15 3:02 ` Nicholas Piggin [this message]
2023-06-15 8:11 ` [kvm-unit-tests v4 00/12] powerpc: updates, P10, PNV support Joel Stanley
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=CTCW1ILCXTMA.24T7LU9PQBTDA@wheely \
--to=npiggin@gmail.com \
--cc=joel@jms.id.au \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
/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).