qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Taylor Edward Heimbichner <theimbichner@email.arizona.edu>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] x86 Instruction Testing?
Date: Wed, 12 Oct 2016 02:19:28 -0700	[thread overview]
Message-ID: <CAFEAcA_iAzCE6ReJpxgAnA9zdfRHnsa8SDqAnFyrY+6mDqTwGQ@mail.gmail.com> (raw)
In-Reply-To: <CACQafCHQzuMmJtq7C-hu_4MPguMQPwX4Dgy_nvdDb0i1esfZuA@mail.gmail.com>

On 11 October 2016 at 16:51, Taylor Edward Heimbichner
<theimbichner@email.arizona.edu> wrote:
> I'm a student researcher with the University of Arizona's Computer Science
> Department. 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.

My suggestions would be one of:
(a) extend the 'risu' tool
https://git.linaro.org/people/peter.maydell/risu.git/blob/HEAD:/README
to handle x86

(b) look at valgrind's test suite, which is much more comprehensive
than QEMU's is.

NB: neither of these makes any attempt at testing 'system'
instructions, only those which can be used by a userspace
binary.

thanks
-- PMM

      parent reply	other threads:[~2016-10-12  9:19 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
2016-10-12  9:19 ` Peter Maydell [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-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=CAFEAcA_iAzCE6ReJpxgAnA9zdfRHnsa8SDqAnFyrY+6mDqTwGQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --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).