From: Dan Williams <dan.j.williams@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: "fuego@lists.linuxfoundation.org"
<fuego@lists.linuxfoundation.org>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Some ideas on open source testing
Date: Thu, 27 Oct 2016 08:39:05 -0700 [thread overview]
Message-ID: <CAPcyv4i2BV9i=CA=R=gHNFk5z4gEVhLmJSpYx-wV_Kam1L_nRQ@mail.gmail.com> (raw)
In-Reply-To: <20161024164116.GB17252@sirena.org.uk>
On Mon, Oct 24, 2016 at 9:41 AM, Mark Brown <broonie@kernel.org> wrote:
[..]
>> Maybe that would be a 90% solution for many file system and even
>> device driver authors, assuming the necesary SOC IP blocks could be
>> emulated by qemu.
>
> qemu emulation isn't really that useful for driver testing, the quality
> of the emulation with respect to the hardware is generally not super
> hot.
The other problem with emulation is testing corner cases and failures.
I doubt the qemu project would want to carry deliberately broken
emulations just for test purposes. This is why I ended up using
interface mocking (the '--wrap=' linker option) for the libnvdimm unit
test suite.
I have found this method effective for testing device-driver routines
in the absence of hardware.
next prev parent reply other threads:[~2016-10-27 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 17:15 Bird, Timothy
2016-10-22 1:19 ` Theodore Ts'o
2016-10-24 16:41 ` Mark Brown
2016-10-27 15:39 ` Dan Williams [this message]
2016-10-27 21:15 ` Guenter Roeck
2016-10-27 21:34 ` Dan Williams
2016-10-27 6:07 ` Amit Kucheria
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='CAPcyv4i2BV9i=CA=R=gHNFk5z4gEVhLmJSpYx-wV_Kam1L_nRQ@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=broonie@kernel.org \
--cc=fuego@lists.linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.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