From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Laurent Desnogues <laurent.desnogues@gmail.com>
Subject: Re: [Qemu-devel] [RFC] ARM test generator
Date: Tue, 8 Jul 2008 16:28:48 +0100 [thread overview]
Message-ID: <200807081628.49314.paul@codesourcery.com> (raw)
In-Reply-To: <761ea48b0807080752m729b9892sd997347f6f4462b9@mail.gmail.com>
> For test-ref.txt generation, the solution is trivial: use real hardware.
> As long as you are not testing unpredictable or implementation
> defined behaviours, that can be considered as a reference that
> qemu should match.
For any reasonable coverage test I'd expect test-ref.txt to be huge, which
makes testing without reference hardware infeasible (and certainly not
suitable for inclusion in qemu SVN). AFAIK For ARMv7 then there are currently
zero generally available hardware platforms, and ARMv6 hardware is still
fairly rare.
Paul
next prev parent reply other threads:[~2008-07-08 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 12:35 [Qemu-devel] [RFC] ARM test generator Laurent Desnogues
2008-07-08 13:26 ` Paul Brook
2008-07-08 14:52 ` Laurent Desnogues
2008-07-08 15:28 ` Paul Brook [this message]
2008-07-08 15:48 ` Laurent Desnogues
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=200807081628.49314.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=laurent.desnogues@gmail.com \
--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).