From: Richard Henderson <richard.henderson@linaro.org>
To: David Gibson <david@gibson.dropbear.id.au>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tcg/ppc: Add vector opcodes
Date: Wed, 27 Feb 2019 16:47:30 -0800 [thread overview]
Message-ID: <bf117507-a3da-9dcd-e2c1-031312b7d89e@linaro.org> (raw)
In-Reply-To: <20190224233142.GC7668@umbus.fritz.box>
On 2/24/19 3:31 PM, David Gibson wrote:
> I have access to POWER8 and POWER9 machines, but I haven't worked with
> RISU before. If you can give me a straightforward recipe I can try
> running the tests.
From
https://git.linaro.org/people/peter.maydell/risu.git
First you need to generate the test cases. It looks like the current
ppc64.risu file is fairly complete, at least to some level. So:
mkdir ../risu-testcases-ppc64
./scripts/generate_all.sh ppc64.risu ../risu-testcases-ppc64
Then record traces from real hardware to compare against:
RISU=`pwd`/risu ./scripts/record_traces.sh ../risu-testcases-ppc64/*.bin
Now compare QEMU against hardware:
QEMU=qemu-ppc64 RISU=`pwd`/risu \
./scripts/run_risu ../risu-testcases-ppc64/*.bin
Which is all hunky dory until something fails. At which point it's a matter of
using qemu's -d and -dfilter options judiciously, and "objdump -b binary -m
ppc64 -D foo.bin".
r~
next prev parent reply other threads:[~2019-02-28 0:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 5:59 [Qemu-devel] [PATCH] tcg/ppc: Add vector opcodes Richard Henderson
2019-02-22 17:13 ` Mark Cave-Ayland
2019-02-22 20:20 ` Richard Henderson
2019-02-24 23:31 ` David Gibson
2019-02-28 0:47 ` Richard Henderson [this message]
2019-02-28 4:01 ` David Gibson
2019-02-28 5:11 ` Richard Henderson
2019-02-27 15:45 ` no-reply
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=bf117507-a3da-9dcd-e2c1-031312b7d89e@linaro.org \
--to=richard.henderson@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=mark.cave-ayland@ilande.co.uk \
--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).