From: Paolo Bonzini <pbonzini@redhat.com>
To: Taylor Edward Heimbichner <theimbichner@email.arizona.edu>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] x86 Instruction Testing?
Date: Wed, 12 Oct 2016 08:59:48 +0200 [thread overview]
Message-ID: <3c2a8689-c62f-5a4e-332d-13cf2b78a916@redhat.com> (raw)
In-Reply-To: <CACQafCHQzuMmJtq7C-hu_4MPguMQPwX4Dgy_nvdDb0i1esfZuA@mail.gmail.com>
On 12/10/2016 01:51, Taylor Edward Heimbichner wrote:
> I'm writing to ask if any executable that you use to test QEMU
> systematically tests all, or at least a large portion, of the x86
> instruction set? We're working on a project that involves dynamic taint
> analysis and would like to use an executable like this to comprehensively
> test our work. Thank you.
There is tests/tcg/test-i386. It doesn't cover newer instructions, but
I tried it just now and it was enough to find a couple bugs, so it
cannot be that bad!
Paolo
next prev parent reply other threads:[~2016-10-12 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 23:51 [Qemu-devel] x86 Instruction Testing? Taylor Edward Heimbichner
2016-10-12 6:59 ` Paolo Bonzini [this message]
2016-10-12 9:19 ` 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=3c2a8689-c62f-5a4e-332d-13cf2b78a916@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=theimbichner@email.arizona.edu \
/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).