From: Stefan Hajnoczi <stefanha@gmail.com>
To: Alexander Graf <agraf@suse.de>
Cc: lmr@redhat.com, "Michael Tokarev" <mjt@tls.msk.ru>,
qemu-devel <qemu-devel@nongnu.org>,
"Michael Roth" <mdroth@linux.vnet.ibm.com>,
"Andreas Färber" <andreas.faerber@web.de>,
gollub@b1-systems.de
Subject: [Qemu-devel] Re: Buildbot for qemu.git/master
Date: Mon, 7 Feb 2011 15:26:09 +0000 [thread overview]
Message-ID: <AANLkTimdrRitpmtkNpxGCJvmycaTCZn_icHHW09_agoZ@mail.gmail.com> (raw)
In-Reply-To: <1F444447-56AF-43A3-BF71-4378456F465D@suse.de>
On Mon, Feb 7, 2011 at 2:44 PM, Alexander Graf <agraf@suse.de> wrote:
> On 07.02.2011, at 15:36, Stefan Hajnoczi wrote:
>> On Mon, Feb 7, 2011 at 1:00 PM, Alexander Graf <agraf@suse.de> wrote:
>>> This is great - thank you! I'll try to get some ppc and s390x VMs set up to run this. Do you have any plans to also integrate actual testing of the compiled code?
>>
>> Cool :). Yes testing can be added after build. Are there specific
>> automated tests you're thinking of?
>
> Nothing specific, just making sure that basic device emulation works and maybe try to run some linux-user binaries too.
Michael Roth recently posted the "qtest" patchset which begins to
enable device model testing:
http://www.mail-archive.com/qemu-devel@nongnu.org/msg54191.html
It goes in the direction of making emulated devices (like AHCI)
testable without running an actual guest. Your test code runs in a
native-code vcpu thread and can interact with the device model via
mmio, pio, DMA, and interrupts.
If you are interested please check out Michael's email thread on qtest.
Or if you meant tests that run small guests to check that networking,
disk, etc still work, then I think KVM-Autotest is what exists today.
Stefan
next prev parent reply other threads:[~2011-02-07 15:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 16:36 [Qemu-devel] Buildbot for qemu.git/master Stefan Hajnoczi
2011-02-05 20:32 ` [Qemu-devel] " Stefan Hajnoczi
2011-02-07 13:00 ` Alexander Graf
2011-02-07 14:36 ` Stefan Hajnoczi
2011-02-07 14:44 ` Alexander Graf
2011-02-07 15:26 ` Stefan Hajnoczi [this message]
2011-02-08 2:29 ` Lucas Meneghel Rodrigues
2011-02-08 9:23 ` Stefan Hajnoczi
2011-02-08 11:23 ` Lucas Meneghel Rodrigues
2011-02-08 11:26 ` Alexander Graf
2011-02-08 11:28 ` Stefan Hajnoczi
2011-02-08 12:32 ` Alexander Graf
2011-02-07 19:03 ` Luiz Capitulino
2011-02-07 21:18 ` Stefan Hajnoczi
2011-02-07 21:23 ` Alexander Graf
2011-02-07 8:30 ` Daniel Gollub
2011-02-07 9:34 ` Stefan Hajnoczi
2011-02-08 11:14 ` Daniel Gollub
2011-02-08 11:39 ` Stefan Hajnoczi
2011-02-07 15:02 ` [Qemu-devel] " Richard W.M. Jones
2011-02-07 15:15 ` Stefan Hajnoczi
2011-02-08 2:36 ` Lucas Meneghel Rodrigues
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=AANLkTimdrRitpmtkNpxGCJvmycaTCZn_icHHW09_agoZ@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=agraf@suse.de \
--cc=andreas.faerber@web.de \
--cc=gollub@b1-systems.de \
--cc=lmr@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mjt@tls.msk.ru \
--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).